NotFairNotFair
Start now

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 uploads a bounded MP4 (base64 or public HTTPS URL) to the ad-account video library; it does not create a creative or ad.

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 45 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.

  1. 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.

  2. 02

    Prepare an exact operation

    The proposal identifies the account, entity, intended value, and the tool that would execute it.

  3. 03

    Wait for explicit approval

    Execution begins only after the user approves the staged operation.

  4. 04

    Record provenance

    The result includes an operation identifier and is recorded with author, timestamp, and outcome.

  5. 05

    Verify after apply

    Read the entity back after applying. This platform does not receive Google Ads impact snapshots or undo metadata.

  6. 06

    Respect provider limits

    Meta Ads policies, permissions, and API restrictions still apply after approval.

Evidence table

What each safety control prevents

ControlWhat it protects againstWhat the operator sees
Explicit account routingReading or mutating the wrong ad accountNamed account and account ID before action
Typed operationsInvented fields and ambiguous mutation intentA documented Meta Ads tool with validated arguments
Approval gateSilent or autonomous spend changesThe exact staged operation before execution
Operation provenanceUnattributed changesOperation ID, author context, timestamp, result
Honest recoveryClaiming Google Ads undo on a platform that does not have itcreateAdImage uploads supplied PNG/JPEG assets. uploadAdVideo uploads a bounded MP4 (base64 or public HTTPS URL) to the ad-account video library; it does not create a creative or ad.

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 uploads a bounded MP4 (base64 or public HTTPS URL) to the ad-account video library; it does not create a creative or ad.
  • Meta Ads policy, permissions, and API limits still apply after approval.

Frequently asked questions

Can NotFair change Meta Ads without asking me?

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.

Are Meta Ads changes undoable like Google Ads?

No. NotFair does not expose Google Ads-style impact snapshots or undo on Meta Ads. createAdImage uploads supplied PNG/JPEG assets. uploadAdVideo uploads a bounded MP4 (base64 or public HTTPS URL) to the ad-account video library; it does not create a creative or ad.

What is recorded after a write?

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.

How many Meta Ads tools does NotFair expose?

NotFair advertises 45 Meta Ads tools, measured from the production registrar and guarded by a drift test.