X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list cards

x_ads_list_cards

Read-onlyIdempotent

List ad cards in an X Ads account. Filter by card type, ID, URI, or name, with pagination and options to include deleted or 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

TableJSON 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

TableJSON 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.

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 the operation read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond that: native X fields and pagination are preserved, and monetary _micro fields represent millionths of the account currency. There is no contradiction with 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two sentences are short and front-load the primary action, but the second sentence is a grammatical run-on ('account Native X fields') and reads awkwardly. Both sentences carry useful information, but the structure could be cleaner.

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?

Given the rich input schema, safety annotations, and presence of an output schema, the description is largely complete. It adds valuable response-format details about pagination and _micro units, though it could be more complete with explicit alternative routing or clarification of 'Native X fields'.

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 coverage is 100%, so all 11 parameters are already documented with descriptions, including pagination and filtering semantics. The description's _micro note relates to response fields rather than input parameters, so it adds little parameter-level meaning beyond the schema.

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 clearly states the verb 'List', the resource 'cards', and the scope 'in an ads account'. This distinguishes it from siblings like x_ads_get_card, which retrieves a single card, and from other list tools operating on different resources.

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 explicit guidance is given on when to use this tool versus alternatives, such as x_ads_get_card for a single card. The listing action is implied by the name and first clause, but the description does not provide exclusions or routing context.

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