Skip to main content
Glama

xdataapi: X (Twitter) data

Retweeters

get_retweeters
Read-onlyIdempotent

Accounts that retweeted a tweet. 0.5 credit per profile. Not every account tier can read this; a 403 is free.

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": {
      "id": "<id>"
    },
    "name": "get_retweeters"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric tweet id: the digits after /status/ in the tweet URL
countNoPage size, 1 to 200. Default 50.
freshNoRead X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none.
cursorNonext_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"Page size, 1 to 200. Default 50."
    • addedInput schema / properties / id / description
      Added value: +"Numeric tweet id: the digits after /status/ in the tweet URL"
  2. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Bypass the cache. Costs 2x credits."New value: +"Read X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none."
  3. 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 readOnly, idempotent, non-destructive, openWorld, so the bar is lower. The description still adds genuinely useful disclosure beyond them: a credit price of 0.5 per profile returned, the existence of an account-tier permission gate, and the fact that a 403 response is not billed. It stops short of describing the shape of the result set or how paging behaves, which keeps it below a 5.

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 very short sentences with no filler: what it returns first, then cost, then the access failure mode. Front-loaded and appropriately sized for the complexity of the tool.

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 read-only, paginated lookup with no output schema, the description covers cost and permission failure but says nothing about what a returned record contains (user fields? ids only?) or that results are paged via cursor. Adequate to call safely, but thin on what an agent should expect back.

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%, and the four parameters (id, count, fresh, cursor) are each documented in the schema with format, bounds, and defaults. The description adds nothing about parameters, 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 states the exact resource returned: accounts that retweeted a tweet. That is a specific and unambiguous purpose, but it does not distinguish itself from similar engagement tools such as get_quotes or get_replies, so an agent must infer the boundary from names alone.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for retrieving engagement data on a tweet. The tier-access note ('Not every account tier can read this') is a prerequisite rather than routing guidance, so the agent gets no help choosing between this and its siblings.

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.