AdsAgent — Meta Ads MCP

adsets_prepare_budget_change

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

Input Schema

Name	Required	Description	Default
`adset_id`	Yes
`daily_budget`	Yes
`ad_account_id`	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

A3.9/5.0

Behavior4/5

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

Adds real context beyond the annotations: the call is a draft/approval step that "does not change delivery", it reads current Meta settings from the "authorized account", and it returns approval_ref and plan_digest that the confirm tool consumes. Missing are draft lifetime/expiry, whether repeat calls create duplicate drafts, and any rate-limit or permission nuance - though the annotation set already covers the safety profile (destructiveHint=false).

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?

Three tight clauses, front-loaded with the purpose, then the return/apply contract, then the sibling routing. No filler, though the trailing "Prefer entities_prepare_update for new work" is terse to the point of being cryptic given the size of the sibling set.

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 output schema already covers return values and annotations carry the safety profile, so the description only needs the workflow and input contract - which it largely delivers. The gap is on the input side: for a budget-mutating prepare step, nothing explains budget units, validation bounds, or what happens to an unapproved draft.

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 the parameter burden, and it does not. It implies the three inputs (ad set, ad account, daily budget) but never states ID formats, currency or minor-unit semantics for daily_budget, or any minimum-budget constraint - the single most likely source of a bad call.

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 daily-budget change", and immediately bounds the scope ("one ad set", daily budget only). It also distinguishes itself from the apply step (operations_confirm_adset_budget) and the general-purpose sibling (entities_prepare_update), so an agent can place it in the workflow without opening any 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?

Gives clear sequencing ("apply only after approval with operations_confirm_adset_budget") and an explicit alternative ("Prefer entities_prepare_update for new work"). The condition for the alternative, "new work", is left slightly ambiguous - it could mean new budget changes vs. new entities - so it stops short of a clean when/when-not rule.

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?