Twitter241 MCP Server

get_post_likes

Get the list of users who liked a specific post by entering the post ID and desired number of likes. Use cursor for pagination to fetch more.

Instructions

Get Post Likes 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_likes"
  }
}

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.1/5.0

Behavior2/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not state return format, pagination, cursor usage, or any permissions/rate limits, leaving significant behavioral aspects undisclosed.

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, front-loaded sentence with no wasted words. However, it is somewhat under-specified, lacking important contextual details about the parameters, so it does not reach the highest tier of helpful conciseness.

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 explain what the tool returns and how parameters like count and cursor affect results. It does neither, leaving critical context missing for a tool with pagination support.

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?

Schema coverage is 100%, so the baseline is 3. The description only clarifies that the operation is keyed by post ID; it adds no meaning for count or cursor beyond the schema's example values, which are minimal.

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 description unambiguously identifies the action (get), resource (post likes), and key (post ID). It distinguishes itself from sibling tools like get_post_retweets or get_post_comments, which handle different post engagement types.

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 for when to use this tool versus alternatives. While the name implies use with a post ID, it does not mention contexts, prerequisites, or exclusions relative to sibling tools like get_user_likes or get_post_retweets.

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

Deploy Server