Twitter241 MCP Server

get_post_retweets

Get the list of users who retweeted a specific post by providing its ID. Set the number of results with count and use cursor for pagination.

Instructions

Get Post Retweets By Post 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>",
      "count": "<count>"
    },
    "name": "get_post_retweets"
  }
}

Input Schema

Name	Required	Description
`pid`	Yes	Example value: 1552735248026411010
`count`	Yes	Example value: 40
`cursor`	No	Example value:

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?

No annotations are provided, and the description discloses no behavioral details such as read-only status, pagination through the cursor parameter, or the shape of the response. The only information is the action itself, which is already implied by the tool name.

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 sentence with no filler, making it easy to parse. However, it is so terse that it omits necessary context, but that is more a completeness issue than a conciseness issue.

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?

Without an output schema, the description should explain what the tool returns or any pagination behavior, but it only restates the tool's purpose. The presence of a cursor parameter suggests pagination, yet no guidance is given.

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 has descriptions for all parameters, but they only contain example values, not semantic meaning. The tool description adds that 'pid' is the post ID, but 'count' and 'cursor' remain under-specified.

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 uses the verb 'Get' and specifies the resource 'Post Retweets' and access path 'By Post ID', making the core action clear. However, it does not explicitly differentiate from sibling tools like get_post_quotes or get_post_likes, though the term 'retweets' is distinct.

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?

The description provides no guidance on when to use this tool over alternatives such as get_post_quotes or get_post_likes. No context, prerequisites, or selection criteria are given, leaving the agent without a basis for tool choice.

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

Deploy Server