AdsAgent — Meta Ads MCP

ads_replace_creative_confirm

DestructiveIdempotent

Run the change the user just confirmed: set the reviewed media field of one Meta ad from current to approved value

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": "ads_replace_creative_confirm"
  }
}

Input Schema

Name	Required	Description	Default
`new_value`	No
`old_value`	No
`entity_name`	No
`confirm_token`	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"
+  ]
+}

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

B3.3/5.0

Behavior3/5

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

Annotations already disclose that this is destructive, non-read-only, idempotent, and closed-world. The description adds the scope ('one Meta ad') and state transition ('current to approved value'), but it does not explain confirmation-token handling, expiry, or the practical effect on the existing media beyond replacement.

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 a single front-loaded sentence with no wasted text. The action and state transition are stated immediately.

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?

The presence of an output schema and rich annotations reduces what the description must cover, and the core mutation is stated. Still, for a destructive confirm operation with 0% parameter-description coverage, the description leaves gaps around confirm_token semantics and the old/new value parameters.

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%, so the description must carry parameter meaning. It only implicitly maps 'current to approved value' to old_value/new_value and 'just confirmed' to confirm_token, without naming parameters or explaining the required confirm_token, entity_name, or value formats.

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 the reviewed media field of one Meta ad from the current value to the approved value. It distinguishes the confirm step from preparation/denial through 'the user just confirmed,' though it does not explicitly name the sibling prepare/deny tools.

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?

The phrase 'the change the user just confirmed' implies this should be used only after user confirmation, which is useful context. However, it does not explicitly state when not to use it or point to ads_replace_creative_prepare / ads_replace_creative_deny as alternatives.

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?