LinkedIn Ads MCP · safety architecture
Approval is required. Google Ads undo is not implied.
New campaigns and creatives default to draft unless activation is explicit. Writes wait for approval and record provenance. NotFair does not expose a LinkedIn impact snapshot. Images upload from a public URL. Video file upload is out of the current NotFair LinkedIn v1 media helper.
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 42 LinkedIn Ads tools while keeping execution and auditability on the server. Recovery is platform-true. This page does not copy Google Ads impact review onto LinkedIn Ads.
- 01
Inspect live state
The agent reads Campaign groups, campaigns, creatives, targeting, and analytics. 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
Keep new creatives in draft
New campaigns and creatives default to draft unless activation is explicit. Claude should not treat draft as live delivery.
- 06
Respect provider limits
LinkedIn 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 LinkedIn 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 | Images upload from a public URL. Video file upload is out of the current NotFair LinkedIn v1 media helper. |
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 LinkedIn Ads.
- Images upload from a public URL. Video file upload is out of the current NotFair LinkedIn v1 media helper.
- LinkedIn 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. New campaigns and creatives default to draft unless activation is explicit. Writes wait for approval and record provenance. NotFair does not expose a LinkedIn impact snapshot.
No. NotFair does not expose Google Ads-style impact snapshots or undo on LinkedIn Ads. Images upload from a public URL. Video file upload is out of the current NotFair LinkedIn v1 media helper.
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 42 LinkedIn Ads tools, measured from the production registrar and guarded by a drift test.
Continue evaluating
Related evidence
LinkedIn Ads MCP server benchmark
Compare hosted and official options on the write lifecycle actually documented.
Read moreHosted OAuth
NotFair hosts LinkedIn Marketing API OAuth. You authorize Campaign Manager accounts without creating a LinkedIn developer app.
Read moreLinkedIn Ads MCP tool surface
See the live endpoint and 42 LinkedIn Ads tools.
Read more