AIsa X / Twitter

List User Followers

get_twitter_user_followers

Read-onlyIdempotent

List the accounts that follow a given X user, identified by @handle, newest follower first. Returns up to 200 per page by default with has_next_page and next_cursor; each entry is a full user object (handle, name, bio, follower count, verification). Use this for audience analysis, mapping a competitor's follower base, or finding influential followers. For the reverse direction (who this user follows) use get_twitter_user_followings. For only the verified subset use get_twitter_user_verified_followers — note that one takes a numeric user_id, not a handle.

Usage-based billing; Default request estimate: $0.00326 USD (not a fixed price). Account-specific pricing and final settlement may differ.

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

Input Schema

Name	Required	Description
`cursor`	No	Cursor for pagination
`pageSize`	No	Number of followers per page Provider reference (supplier schema): `{"default":200,"type":"integer"}`.
`userName`	Yes	Screen name of the user

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "userName"
+]
```

Changed3 schema fields changedOct 19, 2026

addedInput schema / properties / cursor / description
```
Added value: +"Cursor for pagination"
```

addedInput schema / properties / pageSize

Added value: +{
+  "description": "Number of followers per page\n\nProvider reference (supplier schema): `{\"default\":200,\"type\":\"integer\"}`.",
+  "maximum": 200,
+  "minimum": 20,
+  "type": "integer"
+}

addedInput schema / properties / userName / description
```
Added value: +"Screen name of the user"
```

Changed4 schema fields changedOct 15, 2026

removedInput schema / properties / cursor / description
```
Removed value: -"Cursor for pagination"
```

removedInput schema / properties / pageSize

Removed value: -{
-  "default": 200,
-  "description": "Number of followers per page",
-  "maximum": 200,
-  "minimum": 20,
-  "type": "integer"
-}

removedInput schema / properties / userName / description
```
Removed value: -"Screen name of the user"
```

changedInput schema / required

Previous value: -[
-  "userName"
-]New value: +[]

First observedSep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior. The description adds useful behavioral context beyond annotations: newest-follower-first ordering, default page size of 200, `has_next_page` and `next_cursor` pagination, and that entries are full user objects.

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 front-loaded with purpose and ordering, then follows with pagination behavior, use cases, and sibling alternatives. Every sentence contributes relevant selection or invocation information, aside from required pricing boilerplate.

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

Completeness5/5

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

Given the rich annotations, complete schema descriptions, and presence of an output schema, the description provides everything an agent needs to select and call the tool correctly. It covers purpose, alternatives, pagination behavior, return shape at a high level, and usage scenarios.

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

Parameters4/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 all three parameters. The description still adds meaning by clarifying that the user is identified by '@handle', stating the default page size, and explaining pagination via cursor and `has_next_page`/`next_cursor`.

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 states a specific verb and resource: 'List the accounts that follow a given X user, identified by @handle, newest follower first.' It also clearly distinguishes this tool from sibling tools such as `get_twitter_user_followings` and `get_twitter_user_verified_followers`.

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

Usage Guidelines5/5

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

The description names explicit use cases ('audience analysis, mapping a competitor's follower base, or finding influential followers') and routes the agent to alternatives with conditions: reverse direction uses `get_twitter_user_followings`, verified subset uses `get_twitter_user_verified_followers`, and it notes that the verified variant takes numeric `user_id` rather than a handle.

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

All AIsa X / Twitter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?