AdsAgent — Meta Ads MCP

ads_prepare_status_change

Prepare one ad status change: read current Meta settings in your authorized account and save an approval draft. Returns approval_ref and plan_digest; apply only after approval with operations_confirm_ad_status. This call does not change delivery. Prefer entities_prepare_update for new work

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": {
      "ad_id": "<ad_id>",
      "ad_account_id": "<ad_account_id>",
      "target_configured_status": "<target_configured_status>"
    },
    "name": "ads_prepare_status_change"
  }
}

Input Schema

Name	Required	Description	Default
`ad_id`	Yes
`ad_account_id`	Yes
`target_configured_status`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026
- removedInput schema / properties / connection_context
```
Removed value: -{
-  "pattern": "^mctx_v1_[0-9a-f]{64}$",
-  "type": "string"
-}
```
Changed2 schema fields changedOct 18, 2026
- addedOutput schema / else / else / properties / approval_request / properties / confirm_tool
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / else / else / properties / approval_request / properties / instruction_template_id
```
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"
+}
```
AddedOct 14, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds real context beyond the annotations: readOnlyHint=false could read as a live mutation, but the description states 'This call does not change delivery' and that it saves a draft, plus notes the read of current Meta settings in the authorized account. It stops short of saying what happens to a superseded draft or whether drafts expire.

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?

Four short sentences, front-loaded with the action and scope, followed by the return values, the safety constraint, and the alternative routing. No filler.

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?

The prepare/approve/confirm workflow and key outputs (approval_ref, plan_digest) are covered, and an output schema exists so return detail is not required. The gap is parameter-level meaning for a tool with zero schema coverage, and no note on permissions or draft lifecycle.

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% and the description never mentions ad_id, ad_account_id, or target_configured_status; the ACTIVE/PAUSED enum is only implied by 'status change'. With three undocumented required parameters, the description fails to compensate for the schema gap.

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 ('Prepare one ad status change') plus the exact scope ('one'), and explicitly separates it from the apply step by naming operations_confirm_ad_status. An agent can distinguish it from the confirm sibling without opening either schema.

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 the sequencing rule clearly ('apply only after approval with operations_confirm_ad_status') and names an alternative, entities_prepare_update. The alternative's qualifier 'for new work' is vague, and no explicit when-not-to-use condition is given for existing status changes on ads.

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?