TwitterAPI.io MCP Server

Get Tweet Retweeters

get_tweet_retweeters

Read-only

Fetch users who retweeted a specific tweet (the simple 'retweet' action, not quote-tweets — for those use get_tweet_quotes). Returns user profiles with metadata. Paginates via cursor (~20 per page).

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": "get_tweet_retweeters"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Pagination cursor; omit for first page (~20 per page).
`tweetId`	Yes	Numeric ID of the tweet to fetch retweeters for.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor; omit for first page (~100 per page)."New value: +"Pagination cursor; omit for first page (~20 per page)."

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety and scope are covered. The description adds what annotations cannot: the return payload ('user profiles with metadata') and pagination behavior (cursor, ~20 per page), which shapes how an agent loops. It stops short of stating whether results are ordered or what a terminal cursor looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three compact clauses: purpose, sibling exclusion, and pagination. Front-loaded with the core action and zero filler; every sentence earns its place.

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?

For a two-parameter read tool with no output schema, the description covers purpose, alternative, return shape, and pagination. Minor gaps remain around ordering or what indicates the last page, but nothing blocks a correct call.

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%, with both tweetId and cursor already documented in the schema. The description's '~20 per page' adds a small useful detail about page size but otherwise restates the cursor concept. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

Names a specific verb and resource ('Fetch users who retweeted a specific tweet') and immediately disambiguates the scope by excluding quote-tweets and naming the sibling that covers them. An agent can pick this over get_tweet_quotes without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not condition ('not quote-tweets') plus the named alternative (get_tweet_quotes) to use instead. That is exactly the routing information an agent needs, with no inference required.

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

All TwitterAPI.io MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?