Twitter241 MCP Server

get_user_followers_ids

Retrieve the follower IDs of a Twitter user by username. Supports pagination via cursor, with a maximum of 5,000 IDs per request.

Instructions

GET Followers IDs by Username

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": {
      "username": "<username>",
      "count": "<count>"
    },
    "name": "get_user_followers_ids"
  }
}

Input Schema

Name	Required	Description
`count`	Yes	Maximum count is 5000
`cursor`	No	Example value:
`username`	Yes	Example value: mrbeast

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as pagination via cursor, authentication requirements, rate limits, or return format. The schema mentions count max 5000 but the description adds no behavioral context.

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?

The description is a single, concise phrase, front-loaded with the key action and resource. It is free of filler and easy to parse, earning its place as a minimal yet clear summary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no annotations and no output schema, so the description must carry more weight. With only the phrase 'GET Followers IDs by Username,' critical context is missing: how pagination works, whether the response contains an array of IDs or an object, any prerequisites (e.g., user must be public), and how to handle errors. The description is inadequate for an agent to invoke the tool correctly beyond basic parameter filling.

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?

The input schema covers all three parameters with descriptions (100% coverage), so the baseline is 3. The description adds minimal semantic value beyond saying 'by Username,' which is already evident from the parameter naming. No additional details about count or cursor semantics are provided in the description.

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?

The description clearly states the tool retrieves follower IDs for a given username, using the HTTP verb 'GET'. It distinguishes from sibling tools like get_user_followers (which likely returns full user objects) and get_user_following_ids (which targets following, not followers).

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 guidance is provided on when to use this tool versus alternatives. The description simply states the function without context, exclusions, or alternative suggestions. Sibling tools exist but are not referenced.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server