Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_list_tweets

Get list tweets. Tweets from members of a list. Paginated: use cursor / next_cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>"
    },
    "name": "x_list_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
listIdYesNumeric list ID.
sinceTimeNoOnly items created at or after this Unix timestamp (seconds).
untilTimeNoOnly items created before this Unix timestamp (seconds).
includeRepliesNoInclude replies (`true` / `false`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only discloses pagination. It omits ordering, any result-count ceiling, authentication requirements, and even where next_cursor is surfaced in the response — all of which an agent needs for a multi-page read loop.

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?

Three short fragments with the resource stated first and pagination guidance last; nothing is padded. The telegraphic phrasing ('Get list tweets') is slightly clipped but does not cost clarity.

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 five fully described parameters and no output schema, the definition covers the minimum an agent needs to make a first call and paginate. It is still incomplete for choosing between this and the similar list-timeline sibling, and it says nothing about return shape or volume beyond the cursor note.

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 cursor, listId, sinceTime, untilTime, and includeReplies are already fully documented in the input schema. The description's mention of cursor/next_cursor restates the schema rather than adding format, default, or interaction semantics, so the baseline of 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?

The description names a specific verb and resource ('Get list tweets') and clarifies the scope as 'Tweets from members of a list,' which disambiguates it from a tweet-by-ID lookup. It does not, however, explain how it differs from the sibling tool x_list_tweets_timeline, leaving the agent to guess which of the two list-tweet endpoints to call.

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 only usage guidance concerns pagination mechanics ('use cursor / next_cursor'), not tool selection. There is no statement of when to prefer this over x_list_tweets_timeline or x_tweet_advanced_search, and no prerequisites or exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources