AdsAgent — Meta Ads MCP

adsets_prepare_status_change

Prepare one ad set 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_adset_status. This call does not change delivery. Prefer entities_prepare_update for new work

Input Schema

Name	Required	Description	Default
`adset_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"
+}
```
Changed1 schema field changedOct 13, 2026
- addedInput schema / properties / connection_context
```
Added value: +{
+  "pattern": "^mctx_v1_[0-9a-f]{64}$",
+  "type": "string"
+}
```
AddedOct 8, 2026

TDQS

A4/5.0

Behavior4/5

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

Goes well beyond the annotations: it discloses that the call writes an approval draft but 'does not change delivery', and names the returned handles (approval_ref, plan_digest) required for the confirm step. With readOnlyHint=false and destructiveHint=false already declared, this adds the crucial nuance that the write is a draft, not a live mutation.

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?

Four short sentences with the purpose first, then the return contract, then the safety caveat, then the alternative. Every sentence carries distinct information; only the return-value mention is mildly redundant given an output schema exists.

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→confirm workflow, non-mutating nature, and outputs are all covered, and an output schema means return shapes need no explanation. The remaining gap is that three required parameters, including the enum-typed status, are never explained in prose.

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 supplies no meaning for adset_id, ad_account_id, or target_configured_status beyond the enum in the schema. 'Read current Meta settings in your authorized account' hints at account scoping but does not clarify whether ad_account_id must match the adset's owning account or what the status values mean operationally.

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 set status change') plus the exact side effect ('save an approval draft'), which cleanly distinguishes it from ads_prepare_status_change and campaigns_prepare_status_change by scope. An agent knows what entity it acts on without opening the 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?

Explicitly names the follow-up tool ('apply only after approval with operations_confirm_adset_status') and routes new work elsewhere ('Prefer entities_prepare_update'). It doesn't state when to use this versus the sibling prepare tools for ads/campaigns, but the ad-set scoping plus the named next step covers the main decision.

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?