AdsAgent — Meta Ads MCP

operations_confirm_product_delivery_pause

DestructiveIdempotent

Run the change the user just confirmed in this conversation: set the approved product family campaigns in Meta from active to paused. Requires approval_ref and expected_plan_digest

Input Schema

Name	Required	Description
`approval_ref`	Yes
`entity_count`	No	Number of accepted execution targets. Excluded rows are not counted.
`expected_plan_digest`	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"
+}

Changed2 schema fields changedOct 18, 2026
- changedInput schema / properties / approval_ref / maxLength
```
Previous value: -25New value: +38
```
- changedInput schema / properties / approval_ref / pattern
```
Previous value: -"^appr_[0-9a-f]{20}$"New value: +"^(?:appr_[0-9a-f]{20}|batch_[0-9a-f]{32})$"
```
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"
+}
```
AddedOct 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The description adds useful behavior beyond annotations by clarifying the state transition (active to paused) and the approval prerequisite, which helps interpret destructiveHint=true as a pause rather than deletion. It still omits failure behavior, such as what happens if expected_plan_digest does not match the current plan.

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, starting with the action and then giving the state transition and required parameters. Every clause contributes without unnecessary detail.

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

Completeness3/5

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

For a destructive, approval-gated execution tool, the description covers the core action and required inputs. However, it leaves key parameter semantics unexplained and does not describe failure or mismatch handling, which are important for an agent invoking a confirm-style mutation.

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

Parameters2/5

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

Schema description coverage is only 33%, so the description should compensate, but it merely repeats that approval_ref and expected_plan_digest are required without explaining their meaning. The optional entity_count parameter is not mentioned at all, and the digest's role in verification is left implicit.

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

Purpose4/5

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

The description states a specific action and scope: running a previously confirmed change to set approved product family campaigns in Meta from active to paused. It is clear what the tool does, but it does not differentiate from similar confirmation siblings such as products_delivery_pause_confirm or the many operations_confirm_* tools.

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 gives a clear usage context: run the change the user just confirmed in this conversation, and it notes the required approval_ref and expected_plan_digest. However, it does not explicitly state when not to use it or name alternative tools for related confirmation flows.

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?