AdsAgent — Meta Ads MCP

campaigns_prepare_budget_changes

Prepare 1-10 campaign daily-budget changes: read current Meta budgets and save one approval draft. Returns approval_ref and plan_digest; apply only after approval with operations_confirm_campaign_budgets. This call does not change delivery. Prefer entities_prepare_update for new work

Input Schema

Name	Required	Description	Default
`items`	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.4/5.0

Behavior5/5

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

Goes well beyond the annotations: despite readOnlyHint=false it clarifies 'This call does not change delivery', and it explains the draft/approval flow plus the returned approval_ref and plan_digest. That distinction — a non-readonly write that is nonetheless non-delivery-affecting — is exactly the context an agent needs and cannot get from annotations.

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 clauses, front-loaded with the verb+resource and scope, then the return values and the approval gate. The telegraphic style ('Prefer entities_prepare_update for new work') is slightly compressed but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a draft-creating mutation, the description covers what is read, what is persisted, what is returned, what is NOT changed, and how the change is later applied. With an output schema present, return-value detail needn't be repeated, so nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is reported at 0% for the top-level parameter, and the description never explains the `items` array shape (campaign_id / ad_account_id / daily_budget), relying on nested schema text instead. The only added semantics are the 1-10 batch bound, which already exists as minItems/maxItems in the schema.

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 1-10 campaign daily-budget changes') plus the concrete mechanics (read current Meta budgets, save one approval draft). The batch scope (1-10) and draft-only nature distinguish it clearly from campaigns_prepare_budget_change (singular) and from the confirm sibling.

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?

Names the follow-up tool explicitly ('apply only after approval with operations_confirm_campaign_budgets') and offers an exclusion ('Prefer entities_prepare_update for new work'). The phrase 'new work' is a bit vague, but the sequencing guidance around approval is unambiguous.

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?