Twitter241 MCP Server

get_user_verified_followers

Retrieve the verified followers of any Twitter user by their user ID. Specify the user ID and count to get a list of verified accounts following them.

Instructions

Get User Verified Followers By ID. You can get the user(rest_id) query from \

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>",
      "count": "<count>"
    },
    "name": "get_user_verified_followers"
  }
}

Input Schema

Name	Required	Description
`user`	Yes	Example value: 877807935493033984
`count`	Yes	Example value: 20
`cursor`	No	Example value:

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

C2/5.0

Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It does not mention pagination (despite a cursor parameter), rate limits, authentication needs, or what happens on errors. The only behavioral hint is the action 'Get', but that is already implied by the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, which could be seen as concise, but it is incomplete and ends abruptly mid-sentence. The structure lacks front-loaded key information beyond the first phrase, and the trailing fragment is not just wasteful but confusing.

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

Completeness1/5

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

The tool has no output schema and no annotations, so the description must provide complete behavioral context. It only states the core function and a broken hint about the query parameter. This is severely inadequate for a tool with three parameters and a pagination cursor, especially in a large sibling set.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides example values but no semantic explanations. The description adds the context that the 'user' parameter is a 'rest_id', which is marginally useful, but the sentence is cut off. Given the high schema coverage (100%) at a shallow level, the description should have elaborated on how to construct the query, but fails to do so meaningfully.

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 starts with 'Get User Verified Followers By ID', which is a specific verb+resource that clearly indicates the tool's function. It distinguishes from sibling tools like get_user_followers and get_user_followers_ids by explicitly noting 'Verified', though it does not elaborate on how it differs.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. The truncated sentence about obtaining the user(rest_id) query provides no usable context for selecting this tool over siblings, and no exclusions or prerequisites are mentioned.

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

Deploy Server