Skip to main content
Glama

xdataapi: X (Twitter) data

Profile

get_user
Read-onlyIdempotent

Profile of one X user by handle or by numeric user id. Give one of the two. The id stays the same when the user changes the handle. 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
idNoNumeric user id
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.
handleNoHandle, with or without @

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed2 schema fields changed
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Numeric user id",
      +  "pattern": "^\\d{1,19}$",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "handle"
      -]
  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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds two things the annotations cannot: the credit cost ("1 credit") and the key behavioral fact that the numeric id survives handle changes, which tells an agent to prefer id for stable references. Return shape is not described, but with no output schema that is a minor gap for a profile read.

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?

Four short sentences, front-loaded with the resource and lookup keys, then the key selection rule, then the durability tip, then cost. Nothing is redundant with the annotations and no sentence is filler.

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-record read with full schema coverage and read-only annotations, the description covers purpose, key selection, cost, and the one non-obvious behavioral fact (id stability). The only missing element is a note on what the profile contains or how caching affects freshness, which the schema partially covers via fresh.

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 does add real meaning by framing handle and id as mutually exclusive alternatives ("Give one of the two"), which the schema's zero required-parameters does not convey. The fresh/cache trade-off is left entirely to the schema, which documents it well.

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?

"Profile of one X user by handle or by numeric user id" states the resource and its scope (a single user), which implicitly separates it from the batch sibling get_users, and names the two lookup keys. It stops short of explicitly naming the sibling to route against, so an agent must infer the singular/plural distinction.

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" is a useful selection rule for the two lookup keys and fills a gap the schema leaves open (required=0, so the schema alone doesn't say at least one is needed). However, there is no guidance on when to prefer this over get_users or when to pass fresh, so usage is only implied.

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.