Skip to main content
Glama

twitter: Post details

twitter_tweet
Read-only

Post details. One public post with its text, media, likes and replies, plus views and retweets where X shows them. Costs 1 credit.

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": {
      "url": "<url>"
    },
    "name": "twitter_tweet"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPost URL (x.com/user/status/123...) or a bare post id
cache_max_ageNo

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 declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real value on top: it discloses the returned field set, qualifies that views/retweets appear only 'where X shows them', restricts scope to public posts, and states a per-call cost of 1 credit. It does not cover failure modes for private/deleted posts or what cache_max_age does.

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?

Three short sentences, front-loaded with the action, then the return payload, then the cost. Every sentence carries distinct information with no padding or restatement of the name.

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?

With no output schema, the description correctly takes on the burden of describing returns and does so concisely, including conditional fields. The main gap is the undocumented cache_max_age parameter and no note on behavior for protected, deleted, or invalid post URLs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the required url parameter is well documented in the schema itself (URL or bare post id), so the description adds nothing there. The second parameter, cache_max_age, has no description in the schema and is never mentioned in the description, leaving an undocumented knob the agent must guess at.

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-like action (fetch details) and a specific resource (one public post), and enumerates what comes back: text, media, likes, replies, views, retweets. 'One public post' distinguishes it from list-style siblings like twitter_userTweets, though it never names twitter_tweetTranscript as the sibling for full-text extraction.

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?

'One public post' implies the scope (single-post lookup, public only) but there is no explicit when-to-use or when-not-to-use guidance. Nothing routes the agent between this and twitter_tweetTranscript, twitter_userTweets, or twitter_communityTweets; the credit note hints at cost tradeoffs without stating an alternative.

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.