Skip to main content
Glama
Sorsa-io

Sorsa MCP

Official
by Sorsa-io

get_verified_followers

List verified accounts that follow a given X/Twitter user. Use next_cursor to paginate through results.

Instructions

List verified accounts that follow the given user. Use next_cursor to paginate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameNoX/Twitter handle without the @ (provide one of username / user_id / user_link).
user_idNoNumeric X/Twitter user ID.
user_linkNoFull URL of the X/Twitter profile.
next_cursorNoPagination cursor from a previous response.
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only mentions pagination via next_cursor, but lacks disclosure of authentication needs, rate limits, error behavior, or required parameter combinations (e.g., that one of username/user_id/user_link is needed despite schema marking all as optional).

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?

Two sentences, front-loaded with the core purpose, no redundant or unnecessary text.

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?

No output schema and no annotations; the description does not explain return format, mandatory parameter assumptions, error cases, or authentication context. For a tool with many siblings, more guidance is needed for complete understanding.

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 coverage is 100%, so the schema already describes parameters. The description adds marginal value by mentioning next_cursor for pagination, but does not clarify the mutual exclusivity or requirement of identification parameters beyond the schema.

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 explicitly states 'List verified accounts that follow the given user', providing a specific verb and resource, and distinguishes from sibling tools like get_followers (all followers) and get_top_followers (top followers).

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?

The description implies use for verified followers but does not explicitly state when to use this tool versus alternatives like get_followers or get_top_followers, nor does it provide exclusions or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sorsa-io/sorsa-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server