Boost an Instagram Reel with the Meta ads MCP server
Meta's ads MCP server lists boost-eligible Instagram media with ads_get_ig_media and boosts one with ads_boost_ig_post. New ads start paused.
With Meta's ads MCP server, an agent boosts an existing Instagram Reel in three steps: ads_get_ig_accounts finds the linked Instagram account, ads_get_ig_media lists its recent media that is eligible to boost, and ads_boost_ig_post turns the chosen organic post into a boosted ad. Meta says write tools create entities in a paused state and the AI client asks for confirmation before activation.
The tool names and descriptions come from Meta's Ad creation and management page, read 2026-09-29. Sume is not connected to Meta ads. Its part is making the Reel file that you publish first, per the Format runs docs.
Which tools does a boost use?
| Tool | Meta's description |
|---|---|
ads_get_ig_accounts | List Instagram Business or Creator Accounts linked to an ad account |
ads_get_ig_media | List recent media (posts, reels, stories) on an Instagram Business or Creator Account, filtered to boost-eligible items |
ads_boost_ig_post | Turn an existing organic Instagram post into a boosted ad |
ads_get_ad_preview | Render a preview of an ad or creative in a specific placement (Feed, Story, Reels, and so on) |
ads_activate_entity | Change a paused campaign, ad set, or ad to active, which starts spending budget |
Which permission does the Instagram side need?
When you connect with a user access token, Meta's Get started page lists instagram_basic among the permissions to grant, next to ads_management and pages_show_list. The alternative is OAuth, where the MCP client sends you through a Facebook Login for Business dialog instead.
Can the boost tool upload a new video instead?
No: the tool boosts a post that already exists on the Instagram account. Publish the Reel first. Instagram's API fetches a Reel from a public video_url, and a Format run's files are durable, public media.sume.com HTTPS URLs that do not expire. The file rules are in Instagram Reels video requirements for API uploads.
What does the whole flow look like?
Publish the Reel through Instagram, for example with the content publishing API. Then ask the agent to find the account with ads_get_ig_accounts, list boost-eligible media with ads_get_ig_media, and boost the Reel you name. Because ads_get_ig_media filters to boost-eligible items, a Reel that does not appear in the list is not offered by this tool, and this post does not describe a workaround.
The boost arrives paused, like every write from this server, so nothing spends until you confirm activation.
What should I check before I activate?
- Ask for a placement preview with
ads_get_ad_previewin Story and Reels before you activate. - Activation starts spending the budget, per Meta's tool description, so read the campaign and ad set values back first.
- To cap what the agent may change on the account, Meta's ads MCP server has account-level rules that can deny actions such as budget increases; they are in limited availability.
Sources
Related posts
More in Integrations
- Call n8n Workflow Tool not working: video sub-workflow
If an n8n agent says it couldn't run your sub-workflow, publish it: the tool returns 'Workflow is not active' outside the test panel. More checks inside.
- Can Notion send webhooks? Start an AI video job from a page
Yes: Notion's Send webhook action posts page properties to your URL, and integration webhooks report changes. Call Sume from your own endpoint.
- ChatGPT plugins vs MCP server: where does Sume fit?
A plugin is a package that can carry an MCP server. Sume is the server. Here is how the two relate in ChatGPT and Codex, and what a Sume connection still needs.
- Claude Code --callback-port: do you need it for Sume MCP?
No. --callback-port is for servers that need a pre-registered redirect URI. Sume registers clients dynamically, so Claude Code's default random port works.
Written by Sume