Skip to main content
Glama

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

x_tweet_retweeters

Get retweeters. Users who retweeted a tweet. 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": {
      "tweetId": "<tweetId>"
    },
    "name": "x_tweet_retweeters"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
tweetIdYesNumeric tweet ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one real behavioral trait beyond the schema: the result is paginated and the next page is driven by `next_cursor` from the previous response. It says nothing about result ordering, page size limits, rate limits, auth requirements, or what user fields are returned.

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 clauses, front-loaded with purpose, then scope clarification, then the pagination note; nothing is padded. The telegraphic fragment style is terse to the point of reading like notes rather than prose, which slightly costs clarity but wastes no words.

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?

For a two-parameter read tool with no annotations and no output schema, the description covers purpose and the pagination workflow, which is the minimum an agent needs to call it correctly. It leaves the return shape, ordering, and any access constraints unspecified, so it is adequate rather than complete.

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 both parameters are already documented, and the description adds only the pagination loop (`cursor` in, `next_cursor` out) on top of that. It adds no meaning about the `tweetId` format or accepted values beyond what the schema states, 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?

"Get retweeters. Users who retweeted a tweet." gives a specific verb (get) and a precisely disambiguated resource (users who retweeted a given tweet), so an agent can tell this apart from replies/quotes/likes style tools by inference. It does not name or contrast with any sibling tool, which keeps it out of 5 territory.

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?

Usage is implied by the resource definition: call it when you need the set of accounts that retweeted a specific tweet. There is no explicit when-not guidance, no mention of alternatives (e.g. replies or quotes tools), and no prerequisites such as auth or tweet-visibility constraints.

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