Skip to main content
Glama

xdataapi: X (Twitter) data

Quotes

get_quotes
Read-onlyIdempotent

Tweets that quote a tweet, newest first. 1 credit per tweet.

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

Input Schema

NameRequiredDescriptionDefault
idYesNumeric tweet id: the digits after /status/ in the tweet URL
countNoPage size, 1 to 50. Default 20.
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. Changed2 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"Page size, 1 to 50. Default 20."
    • 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
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior, so the description adds real value with two traits not in the structured data: results are returned newest first, and each tweet costs 1 credit. It does not mention that fresh doubles the cost, but the schema covers that.

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 terse sentences with no filler; the result shape is front-loaded and the credit cost follows immediately. Nothing could be removed without losing information.

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 read tool with full schema coverage, an output_schema-free interface, and complete annotations, the description covers the essentials plus ordering and cost. Only minor gaps remain, such as paging workflow and how many results to expect.

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 all four parameters are already documented in the schema, including the id format and the fresh cache behavior. The description adds no parameter-level meaning beyond what is supplied, 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?

Names the specific resource (tweets that quote a given tweet) and its ordering, which distinguishes it from siblings like get_replies and get_retweeters. It lacks an explicit verb, but the resource plus the required tweet id makes the operation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to choose this over related tools such as get_tweet, get_replies, or get_retweeters, and no note on pagination workflow despite a cursor parameter. The agent must infer usage from the name and schema 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.