Twitter241 MCP Server

get_post_quotes

Retrieve quotes of a specific post by providing its ID. Get a list of posts that quote the original tweet, with options for count and pagination.

Instructions

Get Post Quotes 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_quotes"
  }
}

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

B3.2/5.0

Behavior2/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 of behavioral disclosure. It does not mention pagination via cursor, count limits, output shape, or read-only guarantees, offering only the generic word 'Get'.

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?

The description is a single, front-loaded sentence with no redundant words or filler. It is concise and every word contributes to stating the core purpose, even though it sacrifices depth.

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?

With no output schema and no annotations, the description should compensate by explaining return format, pagination behavior, or typical usage, but it does none of these. The tool has three parameters, yet the description only hints at the ID, leaving the overall contract underspecified.

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 100% coverage with example values, so the baseline is 3. However, the description adds no extra meaning for 'pid', 'count', or 'cursor'; it merely echoes 'By Post ID' for the pid parameter while leaving the other parameters functionally unexplained.

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

Purpose5/5

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

The phrase 'Get Post Quotes By Post ID' clearly specifies a verb ('Get'), a resource ('Post Quotes'), and the input identifier, making the operation unambiguous. It also distinguishes itself from sibling tools like get_post_retweets, get_post_comments, and get_post_likes by naming 'Quotes'.

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 versus alternatives, nor does it mention any exclusions or preferred contexts. It simply states what the tool does, leaving the agent without decision support.

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

Deploy Server