Skip to main content
Glama

xdataapi: X (Twitter) data

Thread

get_thread
Read-onlyIdempotent

A tweet with its thread and replies; the focal tweet comes first. 1 credit per tweet returned.

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": {
      "id": "<id>"
    },
    "name": "get_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesNumeric tweet id: the digits after /status/ in the tweet URL
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.
cursorNonext_cursor from the previous page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Numeric tweet id: the digits after /status/ in the tweet URL"
  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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, openWorld and non-destructive, so the safety bar is low. The description adds two genuinely useful behavioral facts not in the annotations: ordering ("the focal tweet comes first") and cost scaling ("1 credit per tweet returned"), which tells the agent that result size drives spend. It stops short of describing paging behavior despite the cursor parameter.

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 with no filler, and the highest-value fact (what the response contains) is front-loaded before the cost note. Every clause carries information an agent can act on.

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?

There is no output schema, so the description carries the return-shape burden, and it only partially does so: it covers ordering and credit cost but says nothing about how many tweets a page contains or how to detect the end of a thread when using cursor. Given the low parameter count and strong annotations, this is adequate but leaves real gaps for a paged, variable-size response.

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%, so id, fresh and cursor are already fully documented in the schema, including the 2x credit cost for fresh. The description adds no parameter-level meaning beyond what the schema provides, 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 uses a concrete verb-and-resource framing ("a tweet with its thread and replies") that makes the returned entity clear and distinguishes it from a plain single-tweet fetch or a replies-only fetch. It does not name the sibling it is contrasted with (get_tweet, get_replies), so differentiation is implicit rather than explicit.

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?

The phrase "with its thread and replies" implies when this is the right choice over a single-tweet call, but there is no explicit when-to-use or when-not-to-use statement and no named alternative. An agent must infer the selection rule from the output description alone.

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.