Skip to main content
Glama

xdataapi: X (Twitter) data

Follower ids

get_follower_ids
Read-onlyIdempotent

Numeric ids of the followers of a user, no profiles. 0.02 credit per id. Same page as get_followers, so a page read there is a cache hit here. 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": {
      "user": "<user>"
    },
    "name": "get_follower_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesHandle (with or without @) or numeric user id
countNoPage size, 1 to 200. Default 200.
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. Changed1 schema field changed
    • addedInput schema / properties / count / description
      Added value: +"Page size, 1 to 200. Default 200."
  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

A4.4/5.0
Behavior5/5

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

Goes well beyond readOnly/idempotent annotations by disclosing per-id credit pricing (0.02), the shared-page cache relationship with get_followers, and that a 403 incurs no charge. These are exactly the cost and failure-mode facts an agent needs before calling.

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?

Four short sentences, no filler, with the identity of the result front-loaded before cost and caching notes. 'A 403 is free' is terse but informative.

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?

Coverage of cost, caching and error pricing is thorough for a paginated list tool, and the return type (numeric ids, no profiles) is stated despite no output schema. Pagination mechanics are left entirely to the schema's cursor field, which is acceptable.

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 user, count, cursor and fresh are already documented, including fresh's 2x-credit behavior. The description only adds a cache-hit note that indirectly explains when fresh is unnecessary, which is marginal value over the schema.

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?

States a specific resource (numeric follower ids of a user) and explicitly scopes it with 'no profiles', which cleanly distinguishes it from get_followers. An agent can pick between the two without inspecting 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 Guidelines4/5

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

The 'no profiles' qualifier plus the note that it shares a page with get_followers implicitly tells the agent when to prefer this tool (id-only needs, warm cache). It stops short of stating an explicit when-not rule, but the routing signal is clear.

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.