AdsAgent — Meta Ads MCP

launch_confirm

DestructiveIdempotent

Run the change the user just confirmed in this conversation: build the approved campaign structure as a queued task. Requires the exact single-use confirm_token from its prepare, once. Lost token: operations_get_approval; follow its next_action. Replies: results, not approval handles/JSON/debug.

Input Schema

Name	Required	Description
`copies`	No
`ad_count`	No
`currency`	No	Account currency code shown in the approval.
`adset_count`	No
`entity_name`	No
`confirm_token`	Yes
`campaign_count`	No
`campaign_names`	No	Campaign names in the exact order shown in the approval.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 23, 2026

addedInput schema / properties / ad_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / adset_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / campaign_count

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / campaign_names

Added value: +{
+  "description": "Campaign names in the exact order shown in the approval.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

removedInput schema / properties / connection_context

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

addedInput schema / properties / copies

Added value: +{
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "Account currency code shown in the approval.",
+  "type": "string"
+}

addedInput schema / properties / entity_name
```
Added value: +{
+  "type": "string"
+}
```

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

Behavior1/5

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

The description says the confirm_token is 'single-use' and must be used 'once,' which conflicts with idempotentHint=true: an agent cannot tell whether retrying with the same token is safe. This is an annotation contradiction despite otherwise useful details about queued execution and response style.

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?

Front-loaded and compact: it states the action, token requirement, lost-token fallback, and response expectation in a few short clauses with no wasted text.

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 description covers the critical token workflow and response expectation, and annotations/output schema carry mutation safety and return structure. However, it leaves most parameters undocumented and introduces an idempotency ambiguity for a destructive, token-gated 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?

Only confirm_token is explained in the description. The other seven optional parameters, including copies, ad_count, currency, entity_name, and campaign counts/names, are not given meaning beyond the sparse schema, and schema coverage is only 25%.

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 and resource: 'build the approved campaign structure as a queued task.' The 'user just confirmed' wording separates it from denial flows like launch_deny without requiring schema inspection.

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?

Gives clear usage context: run the change the user just confirmed, using the exact confirm_token from its prepare. It also routes lost-token cases to operations_get_approval, though it does not explicitly say when not to use this tool or name other confirm 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?