Skip to main content
Glama

XCROP X (Twitter) data

Get following

get_following
Read-only

Accounts an X account follows, newest first. Costs 1 credit per account 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_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many accounts 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

A3.8/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 description earns credit for adding what they don't cover: result ordering ('newest first') and a per-account credit cost, which lets an agent budget calls. It doesn't mention pagination exhaustion or rate limits, but the core behavioral traits are disclosed.

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 compact sentences with zero filler, front-loading the resource and scope before the cost caveat. Every clause carries information an agent would act on.

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 read-only list tool with full schema coverage and no output schema, this is nearly complete: it covers resource, ordering, and cost. The only gap is the absence of any hint about what fields each account record contains or how pagination terminates.

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 count, cursor, and username are already fully documented in the schema. The description adds only the ordering hint ('newest first'), which is mildly relevant to cursor paging but does not deepen parameter meaning beyond the schema baseline.

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 names the exact resource ('Accounts an X account follows') and its ordering ('newest first'), so an agent can immediately distinguish it from get_followers or check_follow by direction. It stops short of explicitly naming a sibling, but the verb+resource pairing is unambiguous.

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 only implied through the resource name; there is no explicit statement of when to pick this over get_followers or check_follow, nor any prerequisite such as requiring a public account. The cost note gives a reason to be cautious with count, but not a selection rule.

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