Go Shift

X Ads ad groups

x_ads_ad_groups

Read-only

X Ads ad groups (line items) with campaign, objective, status, bid strategy and bid, plus spend, impressions, clicks, engagements and conversions for the period, sorted by spend. Read-only. Default period: last 30 days.

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_ad_groups"
  }
}

Input Schema

Name	Required	Description
`folder`	No	Client folder name.
`account`	No	X Ads account name or ID. Optional when only one is enabled.
`campaign`	No	Optional campaign name or ID to filter.
`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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the exact metric set returned, the spend-descending sort order, and the default 30-day window. It stops short of disclosing row limits, pagination, or whether disabled/archived ad groups appear.

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?

Three short sentences, front-loaded with the resource and returned fields, then the read-only and default-period facts. Nearly every clause earns its place; only the redundant restatement of the 30-day default (also in the schema) is mildly wasteful.

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, the description compensates by enumerating the returned dimensions and metrics and the sort order, which is the key missing structured information. For a simple read-only listing tool this is close to complete; only result-size/pagination behavior is unaddressed.

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 every parameter (folder, account, campaign, date_range, start/end date, language) is already documented with formats and defaults. The description only restates the default period, adding no filtering or precedence semantics beyond the schema — the baseline 3 applies.

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?

The description names the exact resource ('X Ads ad groups (line items)') and enumerates the attributes and metrics returned, including the synonym 'line items' that helps an agent map the term. It is clear this is a reporting/list tool, though it never states how it differs from the sibling x_ads_campaigns aggregation.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or routing to alternatives such as x_ads_campaigns or x_ads_performance. 'Read-only' and 'Default period: last 30 days' only imply that this is for reporting, leaving the agent to infer the choice among sibling analytics tools.

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?