TikTok Ads MCP · safety architecture
Create delivery entities DISABLE unless activation is explicitly requested. Previews check local schema; ad group and ad creates also look up the parent via /campaign/get and /adgroup/get. TikTok validates the create on apply. Writes wait for approval and record provenance. adImageUpload and adVideoUpload accept public HTTPS URLs, not local files. API code must be zero even when HTTP is 200.
Last verified · September 17, 2026 · NotFair product team
The NotFair write contract
NotFair gives an MCP client 96 TikTok Ads tools while keeping execution and auditability on the server. Recovery is platform-true. This page does not copy Google Ads impact review onto TikTok Ads.
The agent reads Campaigns, ad groups, ads, reporting, and creative assets. before recommending a mutation.
The proposal identifies the account, entity, intended value, and the tool that would execute it.
Execution begins only after the user approves the staged operation.
The result includes an operation identifier and is recorded with author, timestamp, and outcome.
Create delivery entities DISABLE unless activation is explicitly requested. Local preview is not TikTok provider validation.
TikTok Ads policies, permissions, and API restrictions still apply after approval.
Evidence table
| 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 TikTok 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 | adImageUpload and adVideoUpload accept public HTTPS URLs, not local files. API code must be zero even when HTTP is 200. |
Limits and honest boundaries
No. Read tools can inspect the account, but write tools wait for explicit approval. Create delivery entities DISABLE unless activation is explicitly requested. Previews check local schema; ad group and ad creates also look up the parent via /campaign/get and /adgroup/get. TikTok validates the create on apply. Writes wait for approval and record provenance.
No. NotFair does not expose Google Ads-style impact snapshots or undo on TikTok Ads. adImageUpload and adVideoUpload accept public HTTPS URLs, not local files. API code must be zero even when HTTP is 200.
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 96 TikTok Ads tools, measured from the production registrar and guarded by a drift test.
Continue evaluating
Compare hosted and official options on the write lifecycle actually documented.
Read moreNotFair hosts TikTok Ads OAuth. You authorize advertiser accounts without building a TikTok developer app for the MCP client.
Read moreSee the live endpoint and 96 TikTok Ads tools.
Read more
