AdsAgent — Meta Ads MCP

operations_confirm_ad_page_replace

DestructiveIdempotent

Run the change the user just confirmed in this conversation: set the reviewed identity field of one Meta ad from current to approved value. Requires approval_ref and expected_plan_digest

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": {
      "approval_ref": "<approval_ref>",
      "expected_plan_digest": "<expected_plan_digest>"
    },
    "name": "operations_confirm_ad_page_replace"
  }
}

Input Schema

Name	Required	Description	Default
`new_value`	No
`old_value`	No
`entity_name`	No
`approval_ref`	Yes
`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.

Changed4 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_name
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / new_value

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "object",
+    "array"
+  ]
+}

addedInput schema / properties / old_value

Added value: +{
+  "type": [
+    "string",
+    "number",
+    "boolean",
+    "object",
+    "array",
+    "null"
+  ]
+}

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

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is structured. The description adds meaningful context by tying execution to a user-confirmed change and requiring an approval reference plus expected plan digest, which signals an approval-gated operation.

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?

The description is short and front-loaded, with the core action stated first and requirements appended. It avoids unnecessary repetition, though the phrase 'reviewed identity field' is slightly abstract for a page-replace operation.

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?

An output schema and annotations are present, and the description covers approval gating and the target change. However, for a destructive confirmation tool with 0% schema parameter descriptions, it leaves important invocation details about non-required parameters and approval/digest handling unclear.

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 0% across 5 parameters, and the description only names the two required gate parameters without explaining their formats or roles. It does not clarify new_value, old_value, or entity_name, leaving most parameter semantics undocumented.

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: run a confirmed change that sets a reviewed identity field on one Meta ad from its current to approved value. It is clearly a confirmation/execution tool rather than a prepare or deny tool, though it does not explicitly name those sibling alternatives.

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

Usage Guidelines3/5

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

It gives clear usage context by saying to run the change the user just confirmed and requiring approval_ref and expected_plan_digest. It does not state when not to use it or explicitly point to prepare/deny/approval-lookup alternatives among the many sibling tools.

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?