Go Shift

Change an X Ads campaign budget

x_ads_update_budget

Destructive

Set an X Ads campaign's daily budget and optionally its total budget. Lowering runs immediately; raising returns a preview first and runs only on a second call with confirm=true after the user agrees.

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": {
      "campaign": "<campaign>",
      "daily_budget": "<daily_budget>"
    },
    "name": "x_ads_update_budget"
  }
}

Input Schema

Name	Required	Description
`folder`	No	Client folder name.
`account`	No	X Ads account name or ID. Optional when only one is enabled.
`confirm`	No
`campaign`	Yes	Campaign name or ID.
`language`	No	Language of the card: the language the user is writing in.
`daily_budget`	Yes	New daily budget in the account currency.
`total_budget`	No	Optional new total (lifetime) budget in the account currency.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds the crucial gating behavior the annotations cannot express: decreases execute immediately while increases are preview-only until a confirmed second call. That is exactly the kind of irreversible-action context an agent needs before invoking a destructive mutation.

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?

Two sentences, zero filler, with the core action first and the consequential conditional behavior second. Every clause carries information the agent must act on.

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?

For a destructive, 7-parameter mutation with no output schema, the definition covers the essentials: what changes, and that one path returns a preview requiring confirmation. It could still note the currency/account-scoping implications or that previews are not persisted state, but nothing critical to calling it correctly is missing.

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

Parameters4/5

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

Schema coverage is 86%, so the baseline is 3, but the description adds real meaning to the otherwise undocumented 'confirm' parameter by linking it to the raise-budget preview flow. The remaining parameters (folder, account, language, budgets) are already described in the schema, so this is a modest bump above baseline rather than a full 5.

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?

The description names a specific verb ('Set') and resource ('an X Ads campaign's daily budget and optionally its total budget'), and the platform qualifier ('X Ads') distinguishes it from the google_ads_update_budget, meta_update_budget and snapchat_update_budget siblings without needing to name them.

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?

It gives clear conditional guidance for the two-step flow: lowering is immediate, raising requires a preview and a second call with confirm=true after user agreement. It stops short of naming alternatives (e.g. x_ads_update_bid) or stating prerequisites such as needed permissions or account selection, so it is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Go Shift 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?