X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads get account stats

x_ads_get_account_stats

Read-onlyIdempotent

Retrieve synchronous X Ads account analytics—impressions, engagements, and spend—for a chosen entity, placement, and time window, with pagination and native fields preserved.

Instructions

Get synchronous analytics (impressions, engagements, spend) for an ads account Native X fields and pagination are preserved; monetary fields ending in _micro are millionths of the account currency.

Input Schema

Name	Required	Description
`entity`	Yes	Entity type to fetch metrics for.
`end_time`	Yes	ISO 8601 end of the metrics window (exclusive).
`placement`	Yes	Placement to scope the metrics to.
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`entity_ids`	Yes	Comma-separated IDs of the entities to fetch metrics for (max 20).
`start_time`	Yes	ISO 8601 start of the metrics window, e.g. 2026-07-01T00:00:00Z.
`granularity`	Yes	Granularity of the returned time series.
`metric_groups`	Yes	Comma-separated metric groups, e.g. ENGAGEMENT,BILLING,VIDEO (max 10; MOBILE_CONVERSION groups mu...

Output Schema

Name	Required	Description	Default
`result`	Yes	Original tool result: parsed JSON when the text is JSON, otherwise the text or multiple MCP content blocks. Provider fields depend on the selected query.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.1.1Oct 30, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "properties": {},
-    "type": "object"
-  },
-  {
-    "items": {},
-    "type": "array"
-  },
-  {
-    "type": "string"
-  },
-  {
-    "type": "number"
-  },
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {},
+    "type": "object"
+  },
+  {
+    "items": {},
+    "type": "array"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]

First observedv1.0.1Sep 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the description only needs to add context — and it does: it discloses that native X fields and pagination structure are preserved, and that monetary fields suffixed _micro are millionths of the account currency. That unit convention is real behavioral information an agent cannot get from the annotations, though rate limits and pagination mechanics remain unstated.

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?

Two short sentences with no filler, and the core purpose is front-loaded. The second sentence is slightly run-on ('account Native X fields') and could be split, but nothing is wasted.

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?

An output schema exists, so return-value shape need not be described, and the full input schema covers all required parameters with constraints. The description supplies the two things structured fields cannot: the preserved-pagination/native-field behavior and the _micro monetary unit convention.

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 one of the eight required parameters is already documented, including enum constraints for entity, placement and granularity. The description adds no parameter-level detail beyond the _micro currency convention, which relates to output rather than input, so the schema baseline of 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?

States a specific verb and resource ('Get synchronous analytics (impressions, engagements, spend) for an ads account'), so an agent knows exactly what comes back. It does not differentiate itself from the closest sibling, x_ads_get_campaign_reach, which also returns performance figures.

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 guidance on when to call this versus x_ads_get_campaign_reach or the list/get entity endpoints. The word 'synchronous' hints at a contrast with async reporting, but the agent must infer that; no exclusions or prerequisites are stated.

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