Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_user_followings

Get followings. Accounts a user follows, with full profiles. Up to 100 per page. Paginated: use cursor / next_cursor.

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": "x_user_followings"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
pageSizeNoItems per page, 20 to 100 (default 100). Larger values are treated as 100, smaller as 20.
userNameYesScreen name without the @, e.g. `NASA`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose the key traits: results are paginated, capped at 100 per page, and driven by `cursor` / `next_cursor`. It says nothing about auth requirements, rate limits, or what happens when a user has no followings, leaving real gaps for a no-annotation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short, front-loaded sentences with zero filler; the purpose comes first and pagination last. The telegraphic fragment style ("Get followings.") is slightly abrupt but costs no clarity.

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

Completeness3/5

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

For a 3-parameter, read-only listing tool with no annotations and no output schema, the description covers purpose, return shape ("full profiles"), and pagination. It stops short of describing error conditions, authentication, or result ordering, which an agent would need in the absence of structured metadata.

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 the baseline is 3. The description only restates pagination mechanics already documented in the schema (page cap, cursor/next_cursor) and adds no new meaning, such as guidance on userName formatting or pageSize trade-offs.

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?

"Get followings" is a specific verb+resource, and "Accounts a user follows, with full profiles" disambiguates the direction of the relationship so it isn't confused with followers. It does not explicitly name x_user_followers as the inverse tool, so the differentiation is left partly implicit.

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 phrase "Accounts a user follows" - an agent can infer this is the tool for outbound follows rather than inbound followers. There is no explicit when-to-use / when-not guidance and no named alternative for the inverse lookup.

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