AdsAgent — Meta Ads MCP

operations_confirm_campaign_budget

DestructiveIdempotent

Run the change the user just confirmed in this conversation: set the daily budget of one Meta campaign from the current amount to the approved amount. Requires approval_ref and expected_plan_digest

Input Schema

Name	Required	Description
`currency`	No	Account currency code shown in the approval.
`approval_ref`	Yes
`campaign_name`	No
`new_daily_limit`	No	Approved daily limit in account currency major units, exactly as shown in the approval.
`old_daily_limit`	No	Previous daily limit in account currency major units, exactly as shown in the approval.
`expected_plan_digest`	Yes

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 23, 2026

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

removedInput schema / properties / connection_context

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

addedInput schema / properties / currency

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

addedInput schema / properties / new_daily_limit

Added value: +{
+  "description": "Approved daily limit in account currency major units, exactly as shown in the approval.",
+  "type": "number"
+}

addedInput schema / properties / old_daily_limit

Added value: +{
+  "description": "Previous daily limit in account currency major units, exactly as shown in the approval.",
+  "type": "number"
+}

Changed2 schema fields changedOct 18, 2026
- changedInput schema / properties / approval_ref / maxLength
```
Previous value: -25New value: +38
```
- changedInput schema / properties / approval_ref / pattern
```
Previous value: -"^appr_[0-9a-f]{20}$"New value: +"^(?:appr_[0-9a-f]{20}|batch_[0-9a-f]{32})$"
```
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 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real context beyond that: this executes a previously user-approved change and requires approval_ref and a plan digest, which conveys the guard mechanism. It does not explain what happens if the digest mismatches, but that is a minor gap against the rich 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?

Front-loads the action, then the scope, then the hard preconditions in a tight two-part statement with no filler. Efficient and well ordered.

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?

With an output schema present, return values need no explanation, and annotations carry the safety profile. The description supplies purpose, when-to-use context, and required guards; the only residual gap is the unelaborated digest/approval-ref semantics, which the schema also leaves undocumented.

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 coverage is only 50%; approval_ref, expected_plan_digest, and campaign_name have no schema descriptions. The description only restates that the two refs are required (already in the required array) and does not explain their semantics or what the digest protects against, so it fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (set), resource (daily budget of one Meta campaign), and the transition (current to approved amount), scoped to a single campaign. This implicitly distinguishes it from the plural batch sibling operations_confirm_campaign_budgets, though it never names that alternative explicitly.

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?

'Run the change the user just confirmed in this conversation' clearly frames this as the post-approval execution step, and it names the two guard parameters required. It stops short of stating exclusions or pointing to the batch variant for multiple campaigns.

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?