Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_tweet_quotes

Get quote tweets. Tweets that quote a tweet. Paginated: use cursor / next_cursor.

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": {
      "tweetId": "<tweetId>"
    },
    "name": "x_tweet_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
tweetIdYesNumeric tweet ID.
sinceTimeNoOnly items created at or after this Unix timestamp (seconds).
untilTimeNoOnly items created before this Unix timestamp (seconds).
includeRepliesNoInclude replies (`true` / `false`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it only discloses pagination behavior. It says nothing about read-only vs mutating semantics, ordering of results, authentication requirements, rate limits, or what the response contains, all of which matter for a 5-parameter fetch tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the purpose front-loaded and the pagination hint last. The middle sentence restates the name's meaning, which is mildly redundant but genuinely clarifying for the term "quote tweets."

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?

For a five-parameter, no-annotation, no-output-schema tool, the description covers purpose and pagination but omits result shape, ordering, and how the time-window filters interact. It is adequate to call the tool but not complete enough to predict its output.

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 five parameters including sinceTime/untilTime and includeReplies are already documented in the schema. The description only echoes the cursor/next_cursor convention, adding no meaning beyond the structured fields, which is the baseline for full schema coverage.

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 ("Get quote tweets") and even defines the resource ("Tweets that quote a tweet"), so the agent knows exactly what is returned. It does not differentiate from adjacent siblings such as x_tweet_replies or x_tweet_retweeters, which keeps it from a 5.

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?

The only guidance is pagination mechanics ("use `cursor` / `next_cursor`"); there is no statement of when to pick this over the reply, retweeter, or thread-context tools, nor any prerequisite or exclusion. Usage is only inferable from the tool name.

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.

Resources