X MCP Server

by siddheshutd

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

get-home-timeline

Retrieve tweets from your home timeline, with options to exclude replies, retweets, and limit results.

Instructions

Get tweets from your home timeline

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-home-timeline"
  }
}

Input Schema

Name	Required	Description
`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

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does not disclose that the tool requires authentication, returns tweets from the authenticated user's timeline, or any details about pagination, rate limits, or ordering. Minimal behavioral disclosure.

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 extremely concise with one short sentence. However, the brevity sacrifices helpful information. While no fluff, it could be more informative without being verbose.

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?

No output schema is provided, and the description does not explain what the returned data looks like (e.g., list of tweet objects). The description also lacks context about the home timeline concept and authentication needs. Incomplete for effective tool selection.

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 description coverage is 100%, so baseline is 3. The description adds no additional meaning to parameters; it only restates their purpose as already defined in the schema. No defaults, constraints, or examples are provided.

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 'Get tweets from your home timeline' clearly identifies the action (get) and resource (tweets) and scope (home timeline). It implicitly distinguishes from sibling tools like 'get-user-timeline' which targets a specific user's timeline, 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 on when to use this tool versus alternatives such as 'get-user-timeline' or 'get-tweets'. No mention of prerequisites or context. The description is too brief to guide usage decisions.

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