X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads get active entities

x_ads_get_active_entities

Read-onlyIdempotent

Lists which ads entities had metrics change within a specific time window, so you can request account stats only for entities with activity.

Instructions

List which ads entities had metrics change in a time window (use before requesting account stats) 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 check for metric activity.
`end_time`	Yes	ISO 8601 end of the activity window (exclusive); must be a whole hour (minutes and seconds 0).
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`start_time`	Yes	ISO 8601 start of the activity window; must be a whole hour (minutes and seconds 0).
`campaign_ids`	No	Comma-separated campaign IDs to scope the check to (max 200; exclusive with the other ids filters).
`line_item_ids`	No	Comma-separated line item IDs to scope the check to (max 200; exclusive with the other ids filters).
`funding_instrument_ids`	No	Comma-separated funding instrument IDs to scope the check to (max 200; exclusive with the other i...

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.9/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuinely non-structured context: response shape is native X fields with pagination preserved, and money fields suffixed _micro are millionths of the account currency — a unit convention an agent would otherwise mishandle. It does not mention result-size limits or rate limits, keeping it at 4.

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 sentences, front-loaded with purpose before the workflow hint and format notes. Dense but every clause carries information. The parenthetical interrupts the main clause slightly and it packs three distinct ideas (purpose, sequencing, units/format) into very little text without clear separation.

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 an output schema present, return values needn't be spelled out, and the description still adds the useful _micro unit rule and pagination note. Purpose plus sequencing plus format notes cover what an agent needs to select and call it correctly; only edge cases (empty result meaning, window size limits) are 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% and the per-parameter docs are strong (hour-aligned ISO 8601 windows, enum for entity, exclusivity and 200-max on the id filters), so the schema carries the load. The description adds no per-parameter meaning beyond the _micro output convention, so 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?

States a specific verb and resource — lists ad entities whose metrics changed within a time window — which an agent can distinguish from the list_* siblings that enumerate entities outright. It also implicitly contrasts itself with x_ads_get_account_stats via the parenthetical. Slightly indirect phrasing ('which ads entities had metrics change') keeps it from 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?

The parenthetical '(use before requesting account stats)' gives explicit sequencing guidance that routes the agent to call this before x_ads_get_account_stats, which is a real workflow constraint. It stops short of stating when NOT to use it or naming the alternative as a full either/or, so 4 rather than 5.

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