Skip to main content
Glama

XCROP X (Twitter) data

Get quotes of a post

get_tweet_quotes
Read-only

Posts that quote an X post. Costs 15 credits per quote 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_quotes"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many quotes 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

B3.4/5.0
Behavior3/5

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

Annotations already establish that this is a read-only, open-world operation, so the safety profile is covered. The description adds a genuinely contextual fact beyond annotations - the 15-credit cost per quote returned - which matters for call planning. It stops short of describing return shape, pagination semantics, or empty-result behavior, which keeps it at an adequate rather than rich level.

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 what the tool returns and followed by the cost implication. No redundant restatement of the name and every clause carries information an agent would otherwise lack.

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 three-parameter read-only listing tool with full schema documentation and no output schema, the definition covers identity, scope, and cost. The main omission is pagination behavior and what fields quoted posts contain, which costs it the top mark but is not a failure for a tool of this complexity.

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%, with each parameter (count, cursor, tweet_id) already documented including the accepted post-URL form and the max of 100. The description adds no format, syntax, or validation detail beyond that, so the baseline of 3 applies when the schema carries the parameter burden.

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 (posts that quote an X post) tied to the tweet_id parameter, clearly distinguishing it from get_tweet, get_tweet_replies, and get_tweet_retweeters by name. It does not say how it differs behaviorally from search_tweets when quote content is relevant, but the core purpose is 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 when-to-use or when-not-to-use guidance is given; the definition never mentions sibling tools or the condition under which a caller should prefer this over retrieving replies, retweeters, or full post data. The only operational note is a cost figure, which is useful but not selection guidance.

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