X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list cards

x_ads_list_cards

Read-onlyIdempotent

List cards in an X Ads account with native fields and pagination, filtering by search query, card IDs, types, or URIs; supports soft-deleted and legacy cards.

Instructions

List the cards in 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
`q`	No	Search query matching against the card name.
`count`	No	Number of records to return per page (default 100, max 200).
`cursor`	No	Pagination cursor from a previous response.
`sort_by`	No	Sort order as attribute-direction, e.g. created_at-asc or updated_at-desc.
`card_ids`	No	Comma-separated card IDs to fetch specific cards (max 200).
`card_uris`	No	Comma-separated card URIs to fetch specific cards (max 200).
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`card_types`	No	Comma-separated unified card types to filter by, e.g. IMAGE_WEBSITE, VIDEO_WEBSITE, IMAGE_APP, VI...
`with_deleted`	No	Include soft-deleted cards (default false).
`with_total_count`	No	Include the total_count response attribute (default false; exclusive with cursor).
`include_legacy_cards`	No	Include legacy (non-unified) cards in the response (default false).

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

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value beyond that by disclosing that native X field names are preserved and that _micro monetary fields are millionths of the account currency, which an agent would otherwise misread. It stops short of describing default result set size or what the response envelope looks like, but an output schema exists.

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 clauses with no padding and the core purpose front-loaded. The second clause runs on without a separator ('account Native X fields'), which slightly harms readability but not length.

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

Completeness3/5

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

With an output schema and full annotations, most structural burden is carried elsewhere, and the currency-unit note is a genuinely useful addition. However, for an 11-parameter list tool with soft-delete and legacy-card flags, the description never acknowledges that the result set is filtered/opt-in by default, leaving an agent to discover behavior from the schema alone.

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 all eleven parameters are already documented in the schema, making 3 the baseline. The description only reinforces pagination and currency units, adding no semantics for q, sort_by, card_ids, with_deleted, or the exclusivity of with_total_count with cursor.

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 ('List the cards in an ads account'), which clearly distinguishes it from the sibling get_card (single card) at the verb level. It does not, however, explicitly route against other list siblings like x_ads_list_media_library, so the differentiation is only implicit.

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?

No sentence says when to use this instead of x_ads_get_card or the other list tools, and no prerequisites or exclusions are given. The only usage-adjacent hint is that pagination is preserved, which an agent could infer implies cursor-based traversal, but it is not framed as guidance.

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