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

List posts eligible for promotion from an X Ads account, filtered by type, timeline, and IDs, with pagination and native X fields preserved for ad workflows.

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

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

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

Behavior3/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 that native X fields and pagination are preserved and that _micro monetary fields are millionths of the account currency, which is genuine context beyond the annotations, though the currency note looks like family-wide boilerplate for a post-listing endpoint. It says nothing about rate limits or result caps.

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?

Two short sentences with the purpose front-loaded, which is good. However, the second sentence is a run-on missing punctuation ("account Native X fields...") and reads like appended boilerplate rather than tool-specific guidance.

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 present, return values needn't be explained, and annotations cover safety. What is missing is disambiguation from x_ads_list_promoted_posts and an explanation of the NULLCAST default interaction with 'usable for promotion', which materially affects results for a 9-parameter listing tool.

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 nine parameters are documented in the schema itself, and the two enums (tweet_type, timeline_type) carry their own value descriptions. The description adds no parameter-level meaning beyond the _micro convention, so the 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 ("List posts (tweets)") plus a scope qualifier ("usable for promotion by an ads account"), so the operation is unambiguous. It does not, however, distinguish itself from close siblings such as x_ads_list_promoted_posts or x_ads_list_post_previews, leaving the agent to infer the boundary.

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?

The description never says when to choose this over the many other list_* siblings, nor does it state prerequisites (account permissions, why tweet_type is mandatory). There are no exclusions or alternative-naming beyond the implicit 'promotable' framing.

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