Skip to main content
Glama

xdataapi: X (Twitter) data

Following

get_following
Read-onlyIdempotent

Accounts a user follows. 0.1 credit per profile. Not every account tier can read this; a 403 is free.

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": {
      "user": "<user>"
    },
    "name": "get_following"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesHandle (with or without @) or numeric user id
countNoPage size, 1 to 200. Default 50.
freshNoRead X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none.
cursorNonext_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / count / description
      Added value: +"Page size, 1 to 200. Default 50."
  2. Changed1 schema field changed
    • changedInput schema / properties / fresh / description
      Previous value: -"Bypass the cache. Costs 2x credits."New value: +"Read X again and skip the cache. Costs 2x credits for an item that has a cached copy, the normal price for one that has none."
  3. 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 read-only, idempotent, non-destructive, open-world behavior. Beyond that, the description discloses per-profile credit cost, that some account tiers cannot read it, and that a 403 response is not charged — genuinely useful operational context an agent cannot get from the annotations.

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?

Three short sentences, front-loaded with the resource definition, then cost, then access caveat. No filler and nothing redundant with the schema.

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 single-resource list tool with no output schema, the description covers the resource, the cost model, and a notable failure mode. It leaves pagination behavior and return shape implicit, but the schema handles cursor/count semantics adequately.

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 description coverage is 100%, so user, count, fresh, and cursor are all documented in the schema itself. The description adds no parameter-level meaning beyond that, which is the baseline for this dimension.

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 a specific resource ('Accounts a user follows'), which an agent can distinguish from get_followers/get_follower_ids by the direction of the relationship. It does not name the sibling explicitly, so the differentiation rests on the reader's inference.

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 resource name, but there is no explicit 'use this instead of X when...' guidance or note about how pagination across pages should be driven. The cost and tier notes give practical context for deciding whether to call, but not comparative guidance.

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.