Skip to main content
Glama

XCROP X (Twitter) data

Get reposters of a post

get_tweet_retweeters
Read-only

Accounts that reposted (retweeted) an X post. Costs 1 credit per account returned.

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": {
      "tweet_id": "<tweet_id>"
    },
    "name": "get_tweet_retweeters"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many accounts to return (default 100, max 1000)
cursorNonext_cursor from the previous page, to continue
tweet_idYesNumeric tweet (post) id, or the full post URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful non-annotation fact: 'Costs 1 credit per account returned', which lets the agent reason about expensive high-count calls. It omits return shape and pagination mechanics, but the billing note is real added value.

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?

Two short sentences, no redundancy, with the subject and the cost constraint front-loaded. It is arguably over-terse as a sentence fragment, but nothing is wasted.

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 simple read-only list tool with full schema coverage, no output schema, and annotations present, this covers what the tool returns and what it costs. The remaining gaps — return object fields and pagination behavior — are minor and partly carried by the cursor parameter description.

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 count, cursor, and tweet_id are already documented, including the max of 1000 and the next_cursor continuation pattern. The description adds no parameter-level detail (no mention that cost scales with count, for example), 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 resource (accounts that reposted an X post) with the retweet parenthetical clarifying the jargon. An agent can distinguish this from get_tweet_replies or get_tweet_quotes by the resource named, though the description never explicitly contrasts them.

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?

Provides no when-to-use guidance, no prerequisites (e.g., whether the post must be public), and names no alternative tool. The fragment implies its purpose but leaves the agent to infer when to prefer it over get_tweet, get_tweet_replies, or search_tweets.

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