Meta Ads MCP has 97 tools; Sume exposes 52 reviewed reads
Meta's ads MCP listed 97 tools on 2026-09-09. Sume allows 52 exact reviewed reads and excludes 45, since a name or read-only flag is not enough.
Sume's Meta Ads connector does not pass through everything Meta offers. In the review dated 2026-09-09, the official ads MCP inventory had 97 tools on a single page with no next cursor. Sume's policy allows 52 exact reads and excludes 45. A tool's name or a positive read-only annotation alone never authorizes it; the input schema must match a reviewed snapshot.
What the review recorded
The doc docs/architecture/meta-ads-read-catalog.md records the inventory from https://mcp.facebook.com/ads, observed 2026-09-09, using an existing Sumelabs grant with no consent changes. Policy version 2026-09-13.1 lists each tool as allowed or excluded. A compressed JSON evidence file keeps descriptions, schemas and annotations, with no tokens and no private asset responses.
Examples of each side
| Tool | Decision |
|---|---|
ads_get_ad_accounts | allowed |
ads_get_ad_entities | allowed |
ads_insights_performance_trend | allowed |
ads_library_search | allowed |
ads_pixel_event_read | allowed |
ads_update_entity | excluded |
ads_pixel_event_create | excluded |
ads_update_custom_audience_users | excluded |
How a call is validated
Each call validates required types and declared arguments, including nested batch and filter objects. The validator rejects unknown arguments. For ads_get_ad_entities, the object_state argument can select only live or draft reads. A negative read-only or destructive annotation rejects a definition outright, and prose-only annotation differences do not matter as long as the structural input schema matches.
What the tools cover
The reads cover accounts, ads, creative media, insights, audiences, datasets, experiments, catalogs, help and activity. Writes such as updating entities, changing pixel rules or uploading audience rows stay off, so an agent in your workspace can answer "how did this campaign trend" but cannot edit a campaign.
Why this matters when you compare servers
If you add Meta's server directly to a client, the tool list is whatever Meta publishes that day. Through Sume, the list is the intersection of live discovery and the exact reviewed reads. See adding the Meta ads MCP server to Claude Code for the direct route, and note that the tool count in this post is as observed on 2026-09-09, not a live number.
How to read the numbers
The 97 and 52 are a dated snapshot, not a promise. The reviewed doc names the inventory date, and policy versions change when Sume accepts a new schema variant. Treat the allowed list in the repo doc as the source of truth for what an agent can call.
If a tool you need is excluded, the reason is in the table: it either mutates ad data, such as creating or deleting pixel event rules, or it is app-only telemetry that is not meant for a model. Reads that fit the structural rules are the ones that stay.
Related posts
More in Integrations
- Meta Ads MCP: dynamic registration invalid_client_metadata
Meta's ads MCP rejected a direct public-client registration on 2026-09-06 (invalid_client_metadata), so Sume uses a pre-approved Meta client id.
- n8n webhook auth is Basic, Header or JWT: verify Sume's HMAC yourself
n8n's Webhook node offers Basic, Header and JWT auth, none of which checks Sume's HMAC. Verify sume-v1 over timestamp.raw_body in code, 300 second window.
- n8n video workflow: Respond immediately vs Sume's 30-second sync wait
In n8n, use Respond immediately and let Sume call back. Sume's sync mode waits at most 30 seconds, too short for most video jobs, so avoid the last-node wait.
- Notion API image block with a Sume URL: PNG works, WebP is not listed
Notion's external image block needs a directly hosted, public URL, and its file-type list has no WebP. Ask Sume for png or jpeg, then append the block.
Written by Sume