Skip to main content
Glama

List an X user's followers

x_get_followers
Read-onlyIdempotent

List the accounts that follow an X user, using its numeric user ID. Each follower includes the handle, display name, bio, location and follower and following counts. Page through the list with cursor. Read-only: returns public data and changes nothing. Costs 1 credit per request.

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": {
      "userId": "<userId>",
      "count": "<count>"
    },
    "name": "x_get_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesNumber of results to return (1–50). Defaults to 50.
cursorNoThe previous response's `nextCursor`, to fetch the next page. Omit it for the first page.
userIdYesNumeric user ID (rest_id) whose tweets to list, e.g. "44196397". Look it up from a handle with get-user.
cacheOnlyNoReturn only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.
cacheMaxAgeHoursNoAccept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / count
      Added value: +{
      +  "default": 50,
      +  "description": "Number of results to return (1–50). Defaults to 50.",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "userId"
      -]New value: +[
      +  "userId",
      +  "count"
      +]
  2. Changed2 schema fields changed
    • addedInput schema / properties / cacheMaxAgeHours
      Added value: +{
      +  "description": "Accept a cached result scraped up to this many hours ago. A cached result costs no credits, and its `cachedAt` says when it was scraped. When no cached result is that recent, the data is scraped live at the normal price. Leave it out to always scrape live, e.g. 24.",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedInput schema / properties / cacheOnly
      Added value: +{
      +  "description": "Return only a cached result and never scrape live. With `cacheMaxAgeHours`, only a result that recent is returned; without it, the latest cached result of any age. Responds 404, at no cost, when there is none, e.g. true.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond those flags: the cost of 1 credit per request and the set of fields each follower carries, which is valuable given there is no output schema. It does not describe failure modes or truncation behavior, keeping it out of the top band.

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?

Four short, front-loaded sentences: purpose, returned fields, pagination, cost/safety. Nothing is padded, though the 'Read-only: returns public data and changes nothing' clause largely restates readOnlyHint and could be trimmed.

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 present, listing the follower fields is essential and is supplied, along with paging and per-request cost. Missing only edge-case behavior such as protected accounts or errors, which are secondary for a simple paginated read.

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 the schema already documents count, cursor, userId and the two cache fields in detail. The description only reinforces the numeric-ID requirement and cursor paging, adding little beyond the schema; 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 verb and resource: 'List the accounts that follow an X user.' The followers-vs-following distinction is implicit in the name only; the description never routes to the sibling x_get_following, so an agent must infer the difference.

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

Usage Guidelines3/5

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

Gives operational context – use a numeric user ID, page with `cursor`, look the ID up first – but no explicit when-to-use/when-not guidance or named alternative (e.g. x_get_following, instagram_followers). Usage is implied rather than directed.

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