Skip to main content
Glama
strobekiss

x-mcp-lite

by strobekiss

get_user_followers_you_know

Retrieve a list of followers you know for a specified user, showing mutual connections.

Instructions

Retrieves a list of common followers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
cursorNo
user_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/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 states 'Retrieves a list of common followers' with no details on authentication, rate limits, pagination behavior (despite cursor parameter), or what happens when user_id is invalid. The tool's behavior is mostly opaque.

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 a single short sentence, but it is under-specified. It sacrifices necessary details for brevity, making it less useful than it could be. A good structure would front-load key information but still cover essentials.

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?

Given the tool has three parameters (including pagination) and no sibling differentiation, the description is incomplete. It does not explain the concept of 'common followers', the role of 'count' and 'cursor', or the required nature of 'user_id'. An output schema exists but does not compensate for missing behavioral context.

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

Parameters1/5

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

Schema description coverage is 0% and the description does not explain any of the three parameters (user_id, count, cursor). Users must infer their meanings from names alone, which is insufficient for correct invocation.

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 states the tool retrieves a list of 'common followers', which distinguishes it from 'get_user_followers' that retrieves all followers. However, 'common' is ambiguous—it likely means common with the authenticated user, but this is not explicitly stated.

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 like 'get_user_followers', 'get_latest_followers', or 'get_followers_ids'. The description does not specify when this tool is appropriate or when to use other tools.

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/strobekiss/x-mcp-lite'

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