AdsAgent — Meta Ads MCP

adsets_prepare_bid_change

Prepare one ad set bid-amount 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_bid. 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": {
      "adset_id": "<adset_id>",
      "ad_account_id": "<ad_account_id>",
      "bid_amount": "<bid_amount>"
    },
    "name": "adsets_prepare_bid_change"
  }
}

Input Schema

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

A4.3/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing the two-phase approval model (draft saved here, applied only via the confirm tool), the returned artifacts (approval_ref, plan_digest), and the key safety fact that 'This call does not change delivery.' That is exactly the context an agent needs before invoking a non-destructive-but-write-adjacent prepare step.

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 clauses, front-loaded with purpose, then return values, then the safety caveat, then the sibling preference. Every sentence carries information an agent would otherwise have to guess.

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?

Return values are partly explained (though an output schema exists) and the approval workflow is fully covered. The remaining hole is bidding semantics — units/currency of bid_amount and any validation constraints — which matters for correct invocation of a bid change.

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 only implies what the parameters are. It never explains what bid_amount is denominated in (account currency, minor units, cap vs. target bid), nor what form adset_id / ad_account_id take. With all three parameters undocumented elsewhere, the description should compensate and largely does not.

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 + resource + scope: 'Prepare one ad set bid-amount change' and pairs it with the concrete action 'read current Meta settings ... and save an approval draft.' The bid-amount qualifier implicitly separates it from siblings adsets_prepare_budget_change and adsets_prepare_status_change, and the description names both the confirm tool and entities_prepare_update.

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 an explicit sequencing rule ('apply only after approval with operations_confirm_adset_bid') and points to an alternative ('Prefer entities_prepare_update for new work'). The alternative condition 'for new work' is vague and no explicit when-not-to-use is given, so it falls short of full routing guidance.

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?