Skip to main content
Glama

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

x_tweet_replies

Get tweet replies. Replies to 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_replies"
  }
}

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden of explaining behavior. It does disclose that results are paginated and names the cursor/next_cursor handshake, which is genuinely useful behavioral context, but it says nothing about permissions, rate limits, ordering of replies, or depth of threading.

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

Conciseness3/5

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

The definition is short and front-loaded, which is good, but the middle fragment 'Replies to a tweet.' occupies a sentence without adding information. The pagination note is the only sentence that earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with no annotations and no output schema, the description should explain what kind of reply objects come back and roughly how the result is scoped. Instead, it omits the sinceTime/untilTime filtering entirely and never clarifies how this differs from the v2 sibling.

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 the input schema already documents all four parameters, including the cursor protocol and the sinceTime/untilTime bounds. The description adds nothing beyond what the schema provides, so it lands at the baseline for well-covered schemas.

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 first sentence pairs a specific verb with a specific resource (get tweet replies), which is enough for an agent to know the operation. However, there is no differentiation from close siblings such as x_tweet_replies_v2 or x_tweet_thread_context, and the second sentence ('Replies to a tweet.') merely restates the first.

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 description gives no guidance about when to use this tool rather than available alternatives, and no prerequisites such as whether the tweet or author must be public. The only implied usage is that the caller must already have a tweet ID.

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