Skip to main content
Glama

xdataapi: X (Twitter) data

Replies

get_replies
Read-onlyIdempotent

Direct replies to a tweet, one page. 1 credit per reply.

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

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.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds two genuinely useful facts beyond that: the cost model (1 credit per reply) and the fact that results are capped at one page. It does not say whether nested replies are excluded or in what order results return.

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 scope, followed by the cost. Nothing is padded and nothing is repeated from 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 simple paginated read with full schema coverage and rich annotations, the definition covers scope, cost and page limits. It stops short of explaining pagination continuation or how it differs from the thread/quote siblings, which would round it out for an agent choosing between similar endpoints.

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 id, fresh and cursor are all documented in the schema itself. The description's 'one page' phrase hints at the cursor's purpose but adds no new semantics for id or the cache-bypassing fresh flag, so baseline 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?

States a specific verb and resource: it lists the direct replies to a given tweet, and adds the scope limit 'one page'. The word 'direct' implicitly separates it from a full conversation fetch like get_thread, but no sibling is named explicitly.

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 implied rather than stated: 'Direct replies' signals you want top-level replies only, not the whole thread, and 'one page' signals pagination. There is no explicit when-to-use vs. get_thread/get_quotes guidance and no mention of how to continue paging.

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.