Meta Ads MCP by Markifact

Run Write Operation

run_write_operation

Destructive

Execute a write operation that creates, updates, or deletes external data.

Use this tool ONLY for operations marked with requires_approval: true in find_operations results. These are destructive actions like creating campaigns, updating ad statuses, sending emails, etc. operation_id must be an exact Markifact operation ID returned by find_operations for the authenticated user.

APPROVAL REQUIRED: Every call writes irreversibly to the user's live external accounts. Before each invocation, summarize the exact change in plain language (operation, target account/resource, key field values) and wait for explicit user confirmation. Never call without user's confirmation, approval is CRITICAL.

Never call this without first inspecting the schema via get_operation_inputs. Input shapes, nested objects, and field names vary per operation and cannot be guessed. input_data must contain only fields from the get_operation_inputs schema for the same operation_id.

Write-operation tips

Always prefer a dedicated operation when one already matches the task.
Some platforms have a generic fallback operation for create, update, or remove mutations not covered by a dedicated operation, for example gads_mutate for Google Ads. Use the fallback before reporting a missing write feature.

Files

Some operations may return file_id when datasets are too large. You will also receive a small data_preview for context.
You can reference any file ID in other operation inputs using this syntax: {{file-id}}, for example: {"data": "{{file-xe3fw}}"} (exactly as provided—do not modify or invent file ids).
When you pass a file_id to another operation, the file content will be automatically loaded and converted to the correct data type. JSON becomes Python dict/list, CSV/XLSX becomes a list of dicts (rows), and images/binary files become raw bytes. You do not need to handle parsing or conversion—just pass {{file-id}}.
The file ID is for you to move data between operations efficiently. When sharing results with the user, always share links using the get_file_url tool.

Returns JSON with the operation result.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`input_data`	Yes	Dict matching the selected operation's schema from get_operation_inputs. Pass {} if no inputs are needed.
`operation_id`	Yes	Exact Markifact write operation ID returned by find_operations, e.g. "gads_create_campaign", "gads_edit_responsive_search_ad", "meta_ads_update_campaign_budget", "sheets_write_data".

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructive/openWorld/not-readOnly, but the description goes well beyond them: an approval workflow with per-call confirmation, the warning that every call writes irreversibly to live external accounts, the dependency on get_operation_inputs for unknown input shapes, and file_id substitution semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core rule and organized under headed sections, but there is some duplication ('Never call without user's confirmation, approval is CRITICAL' restates the bolded APPROVAL REQUIRED block) and the Files section is lengthy for a tool whose return values are already covered by an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-param, dynamically-typed dispatcher tool, the description covers the full invocation contract: preconditions (find_operations, get_operation_inputs), approval gate, data-passing conventions, and fallback strategy. Return values are covered by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by constraining operation_id to an exact ID returned by find_operations for the authenticated user, requiring input_data to only contain fields from get_operation_inputs for the same operation_id, and explaining the {{file-id}} reference syntax.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Execute a write operation that creates, updates, or deletes external data.' It also implicitly distinguishes itself from the read-side sibling run_operation and names sibling tools (find_operations, get_operation_inputs) that gate its use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing: use ONLY for operations flagged requires_approval: true from find_operations, and never call before inspecting get_operation_inputs. It also names the preferred alternative (dedicated operations first) and the fallback pattern (gads_mutate) before reporting a missing feature.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Meta Ads MCP by Markifact tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?