Go Shift

Change an X Ads ad group bid

x_ads_update_bid

Destructive

Change an X Ads ad group's bid: a max or target bid amount in the account currency, or switch to automatic bidding. Lowering or switching to automatic 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>",
      "ad_group": "<ad_group>",
      "bid_strategy": "<bid_strategy>"
    },
    "name": "x_ads_update_bid"
  }
}

Input Schema

Name	Required	Description
`bid`	No	Bid amount for MAX or TARGET.
`folder`	No	Client folder name.
`account`	No	X Ads account name or ID. Optional when only one is enabled.
`confirm`	No
`ad_group`	Yes	Ad group (line item) name or ID.
`campaign`	Yes	Campaign name or ID.
`language`	No	Language of the card: the language the user is writing in.
`bid_strategy`	Yes	AUTO ignores bid. MAX isn't available for REACH or FOLLOWERS; TARGET only for REACH, FOLLOWERS or WEBSITE_CLICKS.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

The description adds genuinely new behavior beyond the annotations: bid currency, the immediate-vs-preview split, and the two-call confirmation contract for raises. The annotations already flag destructive=true and openWorldHint=true, so the remaining gap is small, but it does not say whether a preview call mutates anything or how long a preview stays valid.

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, front-loaded with the object of the change, then the mode-dependent execution rule. No filler and no repetition of schema content.

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 an 8-parameter mutation with a destructive hint and no output schema, the description covers the key risk (two-phase confirmation before a raise). It is nearly complete; it could state what the preview returns or whether confirm must repeat identical arguments.

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 88%, so the schema already documents most parameters including the bid_strategy enum constraints. The description contributes the confirm flow, which the schema leaves undocumented (confirm has no description), and clarifies bid is in account currency – meaningful but limited added value over a well-covered schema.

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?

"Change an X Ads ad group's bid" names a specific verb and resource, and the enumeration of max bid, target bid, and automatic bidding makes the scope unambiguous. It does not explicitly name a sibling (e.g. x_ads_update_budget) to route between bid changes and budget changes, so it stops short of a 5.

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: lowering a bid or switching to AUTO executes immediately, while raising returns a preview and requires a second call with confirm=true after the user agrees. What is missing is explicit when-not guidance or a named alternative tool for adjacent operations like budget updates.

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?