Skip to main content
Glama

xdataapi: X (Twitter) data

Profiles, batch

get_users
Read-onlyIdempotent

Profiles of up to 100 X users in one call, by handle (handles) or by numeric user id (ids). Give one of the two lists. 1 credit per profile found.

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_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNo1 to 100 numeric user ids. Give this or handles, not both.
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.
handlesNo1 to 100 handles, with or without @. Give this or ids, not both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / handles / description
      Added value: +"1 to 100 handles, with or without @. Give this or ids, not both."
    • addedInput schema / properties / ids / description
      Added value: +"1 to 100 numeric user ids. Give this or handles, not both."
  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. Changed2 schema fields changed
    • addedInput schema / properties / ids
      Added value: +{
      +  "items": {
      +    "pattern": "^\\d{1,19}$",
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "handles"
      -]
  4. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the description adds real value with the pricing model ('1 credit per profile found'). It still omits failure handling, e.g. what happens when a handle does not resolve, and any rate-limit or partial-result behavior.

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 short sentences, front-loaded with the resource and scale before the input options. No filler, and the pricing note is the last thing an agent reads before 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 3-parameter, fully-described schema with annotations covering the safety profile and no output schema, this is nearly sufficient. The remaining gap is return-shape expectations: whether missing or suspended users are silently dropped from the batch.

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; each parameter already documents its own constraints, including the 1-100 limits and the 'this or handles' rule. The description restates the exclusivity rule rather than adding to it, and never mentions the 'fresh' cache-bypass parameter or its 2x credit cost.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource ('Profiles of up to 100 X users') with the batching scope ('in one call') and both accepted identifier forms. The batch/100 framing implicitly separates it from the singular get_user sibling without needing to name it.

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?

'Give one of the two lists' gives a clear operating constraint on mutual exclusivity, and the batch context implies when to use it over a single-user lookup. However, there is no explicit when-to-use or when-not-to-use guidance relative to siblings like get_user or get_followers.

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.