Skip to main content
Glama

XCROP X (Twitter) data

Get followers

get_followers
Read-only

Followers of an X account, newest first. Costs 1 credit per follower returned.

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_followers"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many followers to return (default 100, max 1000)
cursorNonext_cursor from the previous page, to continue
usernameYesX username without @, e.g. elonmusk

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds a genuinely useful behavioral fact not in the annotations: a credit cost of 1 per follower returned, which affects how an agent should set the count parameter. It does not describe pagination mechanics, but the cursor parameter is documented in the schema.

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 short sentences with no filler. Ordering is stated first and the cost constraint follows immediately, so the highest-value facts lead.

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?

For a simple paginated read tool with full schema coverage and annotations, the description covers purpose, ordering, and cost. Slightly incomplete because it does not note that pagination terminates or how to detect the end, though the cursor field is self-explanatory.

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 all three parameters, defaults, and limits are already documented in the schema. The description only reinforces the cost-per-follower implication of count and adds nothing about cursor semantics or username formatting 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?

Specific verb-resource pair: retrieves followers of an X account, with ordering ('newest first') stated. This distinguishes it from get_following, which the name alone could confuse with it.

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?

Usage is implied by the name and the 'followers of an X account' phrasing, but there is no explicit when-to-use guidance or comparison to siblings like get_following or check_follow. An agent must infer the boundary itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources