Skip to main content
Glama

XCROP X (Twitter) data

Get a post

get_tweet
Read-only

One X post with its text, author, counts (likes, reposts, replies, quotes, views) and media. Costs 15 credits.

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

Input Schema

NameRequiredDescriptionDefault
tweet_idYesNumeric tweet (post) id, or the full post URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), and the description adds a genuinely useful operational trait the annotations do not carry: a fixed cost of 15 credits. It still does not say what happens for deleted, protected, or nonexistent post ids, nor whether counts are live or cached.

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 with zero filler: the returned content is front-loaded and the cost is appended as a secondary fact. Nothing repeats the tool name or the schema.

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 one-parameter read tool with no output schema, listing the returned fields substitutes well for a schema and the cost disclosure is a bonus. The remaining gap is failure behavior for missing or inaccessible posts, which an agent would still have to discover at call time.

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% and the schema already documents that tweet_id accepts a numeric id or a full post URL. The description adds no format, validation, or example detail beyond that, 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?

"One X post with its text, author, counts (likes, reposts, replies, quotes, views) and media" names the exact resource and enumerates the returned fields, so an agent knows precisely what it gets back. It stops short of contrasting itself with search_tweets or get_tweet_replies, leaving the single-vs-many distinction to the name alone.

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?

There is no statement of when to call this instead of search_tweets, get_tweet_replies, or get_tweet_quotes. The 15-credit cost hints that this is a paid lookup to use deliberately, but no explicit selection criteria or prerequisites are given.

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