Meta Ads MCP · safety architecture
Approval is required. Google Ads undo is not implied.
Preview the target and intended change, wait for explicit approval, then record operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo on Meta. createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary.
Last verified · September 17, 2026 · NotFair product team
The NotFair write contract
Inspect, propose, approve, record — then stop at what this API supports
NotFair gives an MCP client 40 Meta Ads tools while keeping execution and auditability on the server. Recovery is platform-true. This page does not copy Google Ads impact review onto Meta Ads.
- 01
Inspect live state
The agent reads Campaigns, ad sets, ads, spend, frequency, CPM, CTR, conversions, and audience overlap across Facebook and Instagram. before recommending a mutation.
- 02
Prepare an exact operation
The proposal identifies the account, entity, intended value, and the tool that would execute it.
- 03
Wait for explicit approval
Execution begins only after the user approves the staged operation.
- 04
Record provenance
The result includes an operation identifier and is recorded with author, timestamp, and outcome.
- 05
Verify after apply
Read the entity back after applying. This platform does not receive Google Ads impact snapshots or undo metadata.
- 06
Respect provider limits
Meta Ads policies, permissions, and API restrictions still apply after approval.
Evidence table
What each safety control prevents
| Control | What it protects against | What the operator sees |
|---|---|---|
| Explicit account routing | Reading or mutating the wrong ad account | Named account and account ID before action |
| Typed operations | Invented fields and ambiguous mutation intent | A documented Meta Ads tool with validated arguments |
| Approval gate | Silent or autonomous spend changes | The exact staged operation before execution |
| Operation provenance | Unattributed changes | Operation ID, author context, timestamp, result |
| Honest recovery | Claiming Google Ads undo on a platform that does not have it | createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary. |
Limits and honest boundaries
- Approval reduces accidental execution; it does not make a strategically bad recommendation good.
- NotFair does not expose Google Ads-style impact snapshots or undo for Meta Ads.
- createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary.
- Meta Ads policy, permissions, and API limits still apply after approval.
Frequently asked questions
No. Read tools can inspect the account, but write tools wait for explicit approval. Preview the target and intended change, wait for explicit approval, then record operation provenance. NotFair does not expose Google Ads-style impact snapshots or undo on Meta.
No. NotFair does not expose Google Ads-style impact snapshots or undo on Meta Ads. createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo exists but production availability is gated behind a Graph API version and test-account canary.
The operation log records the operation ID, target account, tool and arguments, authoring user or agent context, timestamp, and outcome. Provenance is not the same as an exact inverse.
NotFair advertises 40 Meta Ads tools, measured from the production registrar and guarded by a drift test.
Continue evaluating
Related evidence
Meta Ads MCP server benchmark
Compare hosted and official options on the write lifecycle actually documented.
Read moreHosted OAuth
NotFair hosts the Meta Marketing API app. You authorize existing ad accounts through OAuth; you do not create a Meta developer app.
Read moreMeta Ads MCP tool surface
See the live endpoint and 40 Meta Ads tools.
Read more