Skip to main content
Glama

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

x_user_batch_info_by_ids

Get users by IDs. Profiles of up to 20 users in one request.

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": {
      "userIds": "<userIds>"
    },
    "name": "x_user_batch_info_by_ids"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdsYes1 to 20 numeric user IDs separated by commas, e.g. `11348282,44196397`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the entire behavioral burden. It discloses only the batch cap and that all IDs resolve in one request; nothing is said about authentication needs, behavior on invalid/suspended/deleted IDs, partial-failure semantics, whether result order matches input order, or the fields a "profile" contains.

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?

Two short, front-loaded sentences with no filler; the resource and the batch cap appear immediately. The second sentence partially duplicates what the schema and first sentence already convey, so it is efficient but not maximally tight.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should say what a returned profile looks like and how incomplete or missing users are represented. Neither is covered, leaving the agent unable to anticipate response shape for a call it can otherwise construct correctly.

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% and the schema already specifies the comma-separated format, the 1–20 range, and an example. The description's "up to 20" restates the schema rather than adding meaning, so the baseline of 3 applies.

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 gives a specific verb and resource ("Get users by IDs") and adds the batch scope (up to 20 profiles per request), so the agent knows exactly what the call returns. It does not name the single-user sibling (x_user_info), so the distinction from that tool must be inferred from the plural/batch phrasing.

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: the 20-user batch limit suggests this is the efficient path when several known IDs are needed, but the description never states when to prefer it over x_user_info or what to do for more than 20 IDs. No exclusions or prerequisites are given.

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