Skip to main content
Glama
Sign In

TwittrAPI

by io.github.twittrapi
OverviewDiscussionsAdmin

Get affiliates

get_user_affiliates
Read-onlyIdempotent

Get the accounts affiliated with an organization, as in the Affiliates tab of its profile. Empty for accounts without affiliates. Paginated.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_user_affiliates"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many users to request per page (default 20). X may return slightly more or fewer.
cursorNoPagination cursor. Leave empty for the first page; pass the next_cursor from a previous result to get the next page.
formatNoResponse format (default simple). simple: compact JSON with flat camelCase tweets and users, about 60% fewer tokens. raw: X's full GraphQL JSON, only needed for fields simple leaves out (cards, polls, edit history, community notes).
userIdNoNumeric X user ID (rest_id). Provide this or username. Using the ID is faster.
usernameNoX handle, used when you do not have the user ID. Provide this or userId.
max_charsNoMaximum characters of JSON to return (default 50000). Longer output is cut with a [TRUNCATED] marker. Lower it to save context, raise it if you need the full response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile needs no restating. The description adds two useful facts beyond that — empty results are valid, and results are paginated — but says nothing about ordering, page sizing behavior, or what fields an affiliate entry carries.

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 compact sentences, front-loaded with the identifying context and followed by the two facts an agent most needs (empty is normal, results are paged). The "Paginated." fragment earns its place; nothing is padded.

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 6-parameter, zero-required read tool with no output schema, the description leaves the return shape unstated — an agent cannot tell whether it gets user objects, IDs, or something else, or whether affiliates are ordered. The pagination and empty-case notes help, but with no output schema the return contract is under-described.

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%, with count, cursor, format, userId/username and max_chars all documented in the schema itself, so the baseline is 3. The description adds no parameter meaning beyond signaling pagination, which the cursor and count schema entries already cover in detail.

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?

States a specific verb and resource ("Get the accounts affiliated with an organization") and anchors it to a concrete surface ("the Affiliates tab of its profile"), which tells an agent this is not follower data. It never names the nearby siblings it could be confused with (get_followers, get_verified_followers), so the differentiation is left 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 only implied through the data concept; there is no explicit when-to-use versus get_followers/get_verified_followers guidance. The one concrete behavioral cue is "Empty for accounts without affiliates," which tells the agent an empty result is not an error, but that is a result note rather than routing guidance.

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

All TwittrAPI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources