X Ads by Get MCP Ads

Overview Schema Source Related Servers Discussions Admin

x ads list account posts

x_ads_list_account_posts

Read-onlyIdempotent

Retrieve posts usable for ad promotion from an X Ads account, with filters for post type, user, or specific tweet IDs and pagination support.

Instructions

List posts (tweets) usable for promotion by 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
`count`	No	Number of records to return per page (1-1000).
`cursor`	No	Pagination cursor from a previous response.
`user_id`	No	Promotable user whose posts to list (defaults to the account's own user).
`trim_user`	No	Return only the author's user ID instead of the full user object (default false).
`tweet_ids`	No	Comma-separated post (tweet) IDs to scope the response to.
`account_id`	Yes	X Ads account ID from X_ADS_ACCOUNT_IDS.
`tweet_type`	Yes	Post type to list (the legacy API requires this filter).
`timeline_type`	No	Scope to promoted-only, organic or all posts (default NULLCAST).
`include_mentions_and_replies`	No	Include mentions and replies in the results (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.7/5.0

Behavior4/5

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

Annotations already establish that the operation is read-only and non-destructive. The description adds useful behavioral detail beyond annotations: 'Native X fields and pagination are preserved' and 'monetary fields ending in _micro are millionths of the account currency.' This helps the agent interpret responses without contradicting 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.

Conciseness4/5

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

The description is short and front-loads the primary purpose in the first clause. However, the second sentence is slightly run-on and unclear ('account Native X fields') which prevents a perfect structure score.

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, full parameter descriptions, output schema, and strong annotations, the description covers the essential purpose and adds important response caveats. It does not discuss sibling selection or edge cases, but the structured data fills most of those gaps.

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 the schema already documents all nine parameters thoroughly. The description adds no new parameter-level meaning; the _micro note concerns response fields, not input parameters. The baseline of 3 applies because the schema carries the burden.

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 a specific resource ('posts (tweets) usable for promotion by an ads account') and a clear action ('List'), so an agent knows what the tool does. It does not explicitly name or contrast siblings like x_ads_list_promoted_posts, but 'usable for promotion' provides some differentiation.

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

Usage Guidelines3/5

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

The purpose phrase implies the natural use case: retrieving posts that are eligible for promotion via an ads account. However, there is no explicit when-to-use guidance, no mention of alternatives, and no exclusions such as 'use list_promoted_posts for already-promoted posts'.

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