Meta Ads MCP server: seven tool categories and where Sume fits

Meta's hosted ads MCP server, at https://mcp.facebook.com/ads, exposes tools in seven categories: reporting, ad creation and management, catalog management, signals and datasets, help and troubleshooting, A/B tests and conversion lift studies, and activity logs. None of those is a video or image generator, so an agent that wants new creative needs a second MCP server, such as Sume's, to make the file first.

The category list comes from Meta's Ads MCP Server page and the Meta Ads AI Connectors announcement, both read on 2026-10-03. Sume's side comes from MCP tools and gates.

What does Meta's page confirm?

The developer page says the server is remote-hosted and works with any MCP-compatible AI agent, and it describes permission-scoped tools. The announcement page dates the launch to April 29, 2026 in open beta, and says a July 16, 2026 expansion added direct connections through developer apps and ads MCP server rules that let portfolio controllers govern what AI agents can do on an ad account.

The pages I fetched do not give the authentication steps, the full tool list, rate limits or whether a tool accepts a video by URL, so this post does not claim any of them.

Which category does what?

The table maps each category to a creative workflow, using only the names Meta lists.

How would Sume sit next to it?

Sume's hosted MCP is at https://mcp.sume.com/mcp. Under OAuth with only mcp:read you see read-only tools; paid and mutating tools such as generate_video, video_trim and timeline_create need mcp:write or an API key, and each needs an idempotency_key. Details are on MCP OAuth and API keys. The docs also offer dry_run=true for a cost preview and an optional max_spend_usd cap.

A sensible split is that the agent calls Sume tools to make and check the file, waits on jobs_wait, reads the result URL with jobs_result, and only then hands the finished asset to the ad step. The Sume side of that loop is below.

• tools_list to see what the session can call.
• generate_video with dry_run=true and an idempotency_key for a cost preview, then the real submit with max_spend_usd.
• jobs_wait then jobs_result to read the finished file URL.

What are the limits of this setup?

Two separate MCP servers do not talk to each other. The agent has to carry the file URL from one to the other, and Meta's page does not confirm which tool accepts it or in what format. Check the tool schema Meta returns before you plan around a particular upload path.

Also keep spend control on both sides. Meta's server rules govern the ad account; Sume's gates govern generation spend. Neither replaces the other. Poll results as described in Jobs and results.