Go Shift

Pause or turn on X Ads campaigns and ad groups

x_ads_set_status

Destructive

Pause (runs immediately) or turn on an X Ads campaign or ad group. Turning on spends money: the first call returns a preview and changes nothing; call again with confirm=true only after the user explicitly 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>",
      "status": "<status>"
    },
    "name": "x_ads_set_status"
  }
}

Input Schema

Name	Required	Description
`folder`	No	Client folder name.
`status`	Yes
`account`	No	X Ads account name or ID. Optional when only one is enabled.
`confirm`	No
`ad_group`	No	Optional ad group (line item) name or ID inside the campaign; omit to change the campaign itself.
`campaign`	Yes	Campaign name or ID.
`language`	No	Language of the card: the language the user is writing in.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The annotations already flag destructiveHint=true and openWorldHint=true, but the description adds what the annotations cannot: pause is immediate, activation is a two-step preview/confirm flow, and activation spends money. It does not disclose what state a campaign must be in to activate, nor what the preview payload contains, so there is a small remaining gap.

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 tight sentences, front-loaded with the action and its immediacy, then the risk/confirmation contract. Every clause carries decision-relevant information and none is padding.

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 no output schema and 7 parameters, the description covers the highest-stakes elements: the confirm gate, money spent on activation, and the campaign-vs-ad-group target distinction. It stops short of explaining the preview's content or how folder/account disambiguation errors are surfaced.

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 71%, so most parameters are documented in the schema. The description still earns credit by supplying the operative semantics for `confirm` (only after explicit user agreement) and by making the status values' real-world effects explicit. It says nothing about folder/account/language scoping, which the schema partially covers.

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 states a concrete verb pair ('Pause ... or turn on') against a specific resource ('an X Ads campaign or ad group'), and the platform-plus-resource scope separates it from the google_ads/meta/snapchat/tiktok status siblings. An agent knows exactly what this tool mutates without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit when-to-use guidance plus the sequencing rule: pause runs immediately, while activation returns a preview that changes nothing and requires a second call with confirm=true only after explicit user consent. The cost implication of activation is called out, leaving nothing important to inference.

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?