Skip to main content
Glama

xdataapi: X (Twitter) data

Followers

get_followers
Read-onlyIdempotent

Followers of a user. 0.1 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": {
      "user": "<user>"
    },
    "name": "get_followers"
  }
}

Input Schema

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

B3.2/5.0
Behavior4/5

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

Annotations only declare it a safe, idempotent, open-world read, but the description adds real operational context: per-profile credit pricing, an access-tier restriction, and the reassuring note that a 403 is free. It still omits cache lifetime and paging behavior beyond what the schema states.

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 sentences, front-loaded with the subject, then cost, then the access caveat. Highly efficient, though the pricing phrase is telegraphic enough to read ambiguously at first pass.

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?

With no output schema, the description carries the cost and access risk while the schema covers paging and freshness. An agent can invoke it correctly, though it has no picture of the returned profile shape.

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 every parameter including the fresh 2x-credit rule and cursor semantics is already documented in the schema. The description adds no parameter-level meaning, which meets but does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Followers of a user" identifies the resource but uses no verb and never says what is returned (profiles vs. ids), even though the sibling get_follower_ids exists. The credit line "0.1 credit per profile" is the only hint that profiles, not ids, come back. Purpose is inferable but not stated.

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?

No when-to-use guidance is given, and no alternative is named despite a sibling that returns the same relationship as ids. The reader must work out the choice between get_followers and get_follower_ids themselves.

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.