Twitter241 MCP Server

get_user_media

Retrieve media posts from a specific Twitter user by ID. Specify count for number of media items and optional cursor for pagination.

Instructions

Get User Media By ID You can get the user(rest_id) query from \

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": {
      "user": "<user>",
      "count": "<count>"
    },
    "name": "get_user_media"
  }
}

Input Schema

Name	Required	Description
`user`	Yes	Example value: 2455740283
`count`	Yes	Example value: 20
`cursor`	No	Example value:

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 9, 2026

TDQS

D1.7/5.0

Behavior1/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention pagination via cursor, return format, rate limits, or that it likely returns tweets with media. The broken sentence 'You can get the user(rest_id) query from ...' hints at an input source but is incomplete and not useful.

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 short but not concise in a useful way; it is truncated mid-sentence ('...from "') and contains a double space. This is under-specification rather than effective brevity. Every sentence should earn its place, but here the content is incomplete.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, no annotations, and a 3-parameter schema, the description must explain what the tool returns and any behavioral details. It does not explain the return value, pagination, or even what 'media' means. This is inadequate for an agent to correctly invoke the tool.

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% (each parameter has a description, albeit just example values). The description adds almost no semantic meaning beyond the schema, but the broken hint about rest_id does touch on the 'user' parameter. Since the schema already lists parameter names and examples, the baseline of 3 is appropriate despite the weak description.

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 restates the tool name ('Get User Media By ID') without clarifying what 'media' means in this context. It does not specify that it likely retrieves tweets with media attachments, nor does it distinguish from sibling tools like get_user_tweets or get_user_likes. The truncated fragment about 'user(rest_id) query' adds confusion rather than clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. It does not mention scenarios such as 'use this to fetch media tweets' or contrast with get_user_tweets or get_user_likes. The description provides no context for selection.

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

Deploy Server