X MCP Server

by siddheshutd

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get-user-timeline

Retrieve tweets from a specific user's timeline. Control results with options to exclude replies or retweets.

Instructions

Get tweets from a specific user's timeline

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": {
      "userId": "<userId>"
    },
    "name": "get-user-timeline"
  }
}

Input Schema

Name	Required	Description
`userId`	Yes	The X user ID to fetch tweets from
`maxResults`	No	Maximum number of results to return
`excludeReplies`	No	Whether to exclude replies
`excludeRetweets`	No	Whether to exclude retweets

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'Get tweets', implying a read operation, but does not mention rate limits, pagination behavior, whether replies/retweets are included by default, or the structure of the response. The maxResults parameter hints at a limit but is not described.

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, clear sentence that front-loads the core action. There is no extraneous information, and every word serves a purpose.

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

Completeness3/5

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

Given that there is no output schema and no annotations, the description is minimally adequate. It does not explain what the return data looks like, how pagination works, or any limitations. For a tool that returns tweets, more detail would be expected for completeness.

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 input schema has 100% description coverage for all four parameters, so the description is not required to add much. However, the tool description does not add any additional meaning beyond what the schema already provides; it merely restates the purpose. A baseline score of 3 is appropriate given full schema coverage.

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 clearly states it retrieves tweets from a specific user's timeline, using a concrete verb and resource. It implicitly distinguishes from sibling tools like get-home-timeline (which is the authenticated user's own timeline) and get-tweets (which may fetch by IDs), but does not explicitly differentiate.

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 on when to use this tool versus alternatives. There is no mention of prerequisites, such as the need for authentication, the format of the user ID, or the context in which this tool is appropriate compared to get-home-timeline or search endpoints.

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