Twitter241 MCP Server

get_tweets_details_by_ids

Retrieve detailed information for multiple tweets by supplying their IDs. Provide comma-separated tweet IDs to fetch their details from the Twitter241 API.

Instructions

Get Tweets Details By Tweet IDs

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": {
      "tweetIds": "<tweetIds>"
    },
    "name": "get_tweets_details_by_ids"
  }
}

Input Schema

Name	Required	Description	Default
`tweetIds`	Yes	Example value: 1892702078029476328,1885213980739711144,1886671728941924567,1905285543136551299

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

C2/5.0

Behavior1/5

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

No annotations are present, so the description carries the full burden. It only says 'Get', implying a read operation, and provides no information about output format, rate limits, authentication, or any other behavioral traits.

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

Conciseness2/5

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

The description is extremely short but this is under-specification, not conciseness. It does not earn its place as it merely restates the tool name with no additional value.

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?

Given the simple schema and no output schema, the description should explain what 'details' includes or clarify the multi-tweet behavior. It remains vague and incomplete, especially with so many sibling tools that overlap in functionality.

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 fully covers the single parameter tweetIds with an example of comma-separated IDs, so the description does not need to add much. The parameter name is self-explanatory, and the example clarifies the expected format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is essentially a sentence-form restatement of the tool name, adding no new information. It fails to distinguish this tool from siblings like get_tweet_details or get_tweet_details_v2, which also fetch tweet details.

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 usage guidance is provided. There is no indication of when to use this tool versus the many sibling tools for similar purposes, nor any mention of alternatives or exclusions.

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

Deploy Server