Go Shift

X Ads performance

x_ads_performance

Read-only

Use this when the user asks how their X (Twitter) Ads account or campaigns are performing. Returns spend, impressions, clicks, CTR, CPC, engagements, conversions (X total conversions), cost per conversion, purchase value and ROAS for the period, the change versus the previous period, a daily trend and a per-campaign table. Read-only. The result is also displayed to the user as a visual dashboard card. Default period: last 30 days (up to 92 days); amounts are in the account's currency.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x_ads_performance"
  }
}

Input Schema

Name	Required	Description
`detail`	No	summary (default): headline numbers and the top 5 rows — right for a specific question or a quick look. full: every row and section — only when the user asks for a full report, a complete list or all the details.
`folder`	No	Client folder name.
`account`	No	X Ads account name or ID. Optional when only one is enabled.
`end_date`	No	YYYY-MM-DD.
`language`	No	Language of the card: the language the user is writing in.
`date_range`	No	Preset period. Default LAST_30_DAYS.
`start_date`	No	YYYY-MM-DD (with end_date).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond annotations: the result is displayed as a dashboard card, the default period is 30 days (up to 92 days), and amounts are in the account currency. It does not mention rate limits or auth, but that is a minor omission given the 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?

The description is front-loaded with the when-to-use condition and the list of returned metrics. It is efficient and avoids waste, though 'Read-only' repeats what the annotations already declare. The remaining sentences earn their place by adding dashboard, default period, and currency context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the burden of explaining return values. It does this thoroughly by listing every metric (spend, impressions, clicks, CTR, CPC, engagements, conversions, cost per conversion, purchase value, ROAS), the previous-period change, daily trend, and per-campaign table. It also covers the default period and currency, making the definition complete for calling and interpreting the tool.

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 description coverage is 100%, so the schema already explains all seven parameters including enum options and formats. The description adds the default period and the 92-day cap for date ranges, which is helpful, but most parameter meaning is already in the schema. Baseline 3 is appropriate.

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 specific verb and resource: reporting performance for X (Twitter) Ads accounts or campaigns. It lists the exact metrics returned and distinguishes itself from sibling performance tools by platform. An agent can immediately tell this is the X Ads analytics tool.

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?

The opening sentence gives clear when-to-use guidance: 'when the user asks how their X (Twitter) Ads account or campaigns are performing.' The detail parameter further clarifies when to use summary versus full mode. It does not explicitly name when not to use it, but the platform-specific scope makes the boundary with other performance tools obvious.

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?