Skip to main content
Glama

XCROP X (Twitter) data

Get replies to a post

get_tweet_replies
Read-only

Replies under an X post (its conversation). Costs 15 credits per reply 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": {
      "tweet_id": "<tweet_id>"
    },
    "name": "get_tweet_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many replies to return (default 10, max 100)
cursorNonext_cursor from the previous page, to continue
tweet_idYesNumeric tweet (post) id, or the full post URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds a genuinely useful non-annotated trait - the credit cost of 15 per reply returned, which lets an agent budget usage. It does not disclose reply ordering, whether nested replies are flattened, or pagination termination behavior.

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, zero waste, with the resource scope front-loaded ahead of the cost note. Nothing is repeated from the schema or annotations.

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 simple three-parameter read tool with full schema coverage and annotations, scope plus cost covers most of what an agent needs. It is still thin on pagination behavior and result ordering, and there is no output schema to fill that gap.

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 tweet_id (id or full URL), count (default 10, max 100), and cursor are already fully documented in the schema. The description adds no additional parameter meaning beyond that, so the 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?

The description states a specific resource and scope: 'Replies under an X post (its conversation)', which concretely distinguishes it from siblings like get_tweet_quotes and get_tweet_retweeters. The retrieval verb is only implied by the parenthetical, so it falls just short of a full verb+resource statement.

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 parenthetical '(its conversation)' implies this is the tool for reading a post's reply thread, which gives implicit usage context. However, it never states when to prefer it over get_tweet_quotes or get_tweet_retweeters, nor any prerequisites such as the post needing to exist or be public.

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