Skip to main content
Glama
Sorsa-io

Sorsa MCP

Official
by Sorsa-io

get_new_followers_7d

Retrieve crypto-focused X/Twitter accounts that followed you within the last 7 days.

Instructions

Get accounts that started following the user in the last 7 days (crypto ecosystem).

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.
Behavior3/5

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

Provides time window and domain context, which is helpful. However, with no annotations, the description carries full burden for behavioral disclosure. It lacks details on data freshness, rate limits, authentication, or pagination. Schema covers identifier alternatives, but overall transparency is moderate.

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?

Single sentence of 10 words, directly stating the tool's purpose. No extraneous information. Extremely concise and well-structured.

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

Completeness4/5

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

Describes the core function (new followers in 7 days) and domain context. As a simple list tool without output schema, it is largely complete. Minor omissions like pagination or result count are not critical for this tool's typical use.

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 schema already covers all three parameters with descriptions (username, user_id, user_link), so the tool's description does not add further parameter-level meaning. Baseline score of 3 is appropriate since schema coverage is 100%.

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?

Description clearly states it retrieves accounts that started following in the last 7 days, with a specific domain context (crypto ecosystem). This distinguishes it from siblings like get_followers (all followers) and get_new_following_7d (following).

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 explicit guidance on when to use this tool versus alternatives. For example, it does not clarify when to use this over get_followers or get_new_following_7d. The 'crypto ecosystem' hint is a domain qualifier, not usage guidance.

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