AdsAgent — Meta Ads MCP

products_delivery_pause_confirm

DestructiveIdempotent

Run the pause the user just confirmed in chat: product-family campaigns active to paused, with the exact pd_confirm_* from its prepare, once. Replies: results, not approval handles/JSON/debug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "confirm_token": "<confirm_token>"
    },
    "name": "products_delivery_pause_confirm"
  }
}

Input Schema

Name	Required	Description	Default
`entity_count`	No	Number of accepted execution targets. Excluded rows are not counted.
`confirm_token`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

removedInput schema / properties / connection_context

Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}

addedInput schema / properties / entity_count

Added value: +{
+  "description": "Number of accepted execution targets. Excluded rows are not counted.",
+  "minimum": 0,
+  "type": "integer"
+}

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.4/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the annotations: it names the state transition, requires the exact confirmation token from prepare, and says the operation should run once. The annotations already declare destructiveHint=true and idempotentHint=true, so the remaining gap is minor.

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

Conciseness5/5

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

The description is compact and front-loaded: it starts with the action and state transition, then gives the token requirement, execution count, and output expectation. Every clause serves the agent's invocation decision.

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?

For a destructive confirm tool with annotations and an output schema, the description covers the critical details: what is paused, which token to use, and that it runs once. It leaves minor gaps around entity_count and the relationship to the operations_confirm_product_delivery_pause sibling, but those are not essential to calling it correctly.

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?

The schema has only 50% description coverage, but the description compensates for the undocumented confirm_token parameter by explaining that it must be the exact pd_confirm_* value from the prepare call. The entity_count parameter is already described in the schema as the number of accepted execution targets.

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?

The description states a specific action: run a user-confirmed product-family campaign pause from active to paused. It distinguishes this from the prepare step by requiring the exact pd_confirm_* token from that prepare, so an agent can identify the confirm operation rather than the preparation operation.

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

Usage Guidelines4/5

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

It clearly says to use this only after the user has confirmed the pause in chat and to use the exact token from the corresponding prepare call. It does not explicitly distinguish this from the similarly named operations_confirm_product_delivery_pause sibling, but the prepare/confirm sequence is clear.

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?