Twitter241 MCP Server

get_tweet_details_v2

Fetch detailed information for any tweet by supplying its ID. Use this tool to access tweet metadata, content, and more.

Instructions

Get Tweet Details By Tweet ID

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": {
      "pid": "<pid>"
    },
    "name": "get_tweet_details_v2"
  }
}

Input Schema

Name	Required	Description	Default
`pid`	Yes	Example value: 1631781099415257088

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely states the action without mentioning what data the details include, whether the operation is read-only, any authentication requirements, or rate limits. This is similar to the 'update_drive' example that scored 2 for lacking critical behavioral context.

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

Conciseness4/5

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

The description is a single, concise sentence that is front-loaded and free of unnecessary words. It earns its place by stating the core action, though it could be enhanced with additional relevant details without becoming verbose.

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 simple one-parameter read tool, the description is minimal. With no output schema and no annotations, it fails to convey what 'details' means in practice or how this v2 differs from the sibling 'get_tweet_details'. This is incomplete for an agent to fully understand the tool's behavior and output.

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?

The schema provides a parameter 'pid' with only an example value, which is not semantically informative. The description's phrase 'By Tweet ID' clarifies that 'pid' is the tweet ID, adding meaning beyond the schema. Since the description covers the intent of the sole parameter, a baseline score of 3 is appropriate.

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 'Get Tweet Details By Tweet ID' uses a specific verb and resource, clearly indicating a single-tweet lookup by ID. However, it does not distinguish itself from the sibling tool 'get_tweet_details', which likely serves a similar purpose, so it falls short of a 5.

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 guidance is provided on when to use this tool versus alternatives such as 'get_tweet_details' or 'get_tweets_details_by_ids'. The description implies usage (provide a tweet ID) but lacks explicit context, exclusions, or alternative recommendations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server