AdsAgent — Meta Ads MCP

products_delivery_pause_prepare

Prepare a pause of live-verifiable ACTIVE campaigns for 1-20 owned product_refs in your authorized Meta accounts; expected_scope=all_live_active_campaigns. Saves an approval draft. Review excluded inventory and budget drift. Prepare does not pause Meta. After approval pass its pd_confirm_* token to products_delivery_pause_confirm

Input Schema

TableJSON Schema

Name	Required	Default
`product_refs`	Yes
`expected_scope`	No	all_live_active_campaigns
`connection_context`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`message`	No
`retryable`	No
`support_ref`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 15, 2026
- addedOutput schema / else / then / properties / category
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / expected
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / else / then / properties / failure_kind
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / responsibility_hint
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / route
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / then / properties / user_visible
```
Added value: +{
+  "type": "boolean"
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
First observedSep 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations are non-committal (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description usefully clarifies that it 'Saves an approval draft' and does NOT execute the pause — resolving the ambiguity of a non-readOnly tool that changes nothing live. It does not mention auth requirements or rate limits, so it is strong but not exhaustive.

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?

Dense but front-loaded: purpose and scope come first, then the critical 'does not pause' caveat, then the hand-off token. Every clause earns its place, though the run-on construction packs several distinct ideas into one block.

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

Completeness4/5

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

With an output schema present, return values need no explanation, and the description covers the workflow, the review checks, and the next tool. The only gap is the unexplained connection_context parameter.

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

Parameters3/5

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

Schema coverage is 0%, so the description must carry the load. It adds the meaningful 1-20 count constraint on product_refs and restates expected_scope=all_live_active_campaigns, but connection_context (the mctx_v1_* auth token) is never explained in either place.

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 ('Prepare a pause'), a precise resource ('live-verifiable ACTIVE campaigns'), and scope bounds ('1-20 owned product_refs in your authorized Meta accounts'). It is immediately distinguishable from the confirm/deny siblings and from campaign-level pause tools.

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?

Explicitly routes the agent: 'Prepare does not pause Meta' clarifies this is a draft step, and it names the follow-up tool ('pass its pd_confirm_* token to products_delivery_pause_confirm'). It also flags the review actions (excluded inventory, budget drift) the agent should perform before confirming.

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

All AdsAgent — Meta Ads MCP 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?