Twitter MCP Server

get_home_timeline

Retrieve recent tweets from accounts you follow in newest-first order, with optional count and time filters for focused timeline checks.

Instructions

Get recent tweets from accounts you follow (your home timeline), newest first. Requires a paid X API tier (Basic or higher).

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
`count`	No	Optional: number of tweets to return (1-100, defaults to the API default of 100)
`since_days`	No	Optional: only return tweets from the last N days (e.g. 1, 3 or 7). Cannot be combined with start_time
`start_time`	No	Optional: only return tweets created after this ISO 8601 UTC timestamp (e.g. 2024-01-01T00:00:00Z). Cannot be combined with since_days

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.3.0Nov 4, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden. It usefully discloses ordering (newest first) and a cost/auth constraint (paid X API tier, Basic or higher), but says nothing about pagination, rate limits, or what a failed tier check looks like.

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?

Two short sentences with the operation and ordering front-loaded and the tier prerequisite second. Nothing is wasted or redundant.

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?

For a 3-optional-parameter read tool with no output schema, the description covers purpose, ordering, and the access-tier constraint. It omits pagination behavior and result-shape expectations, which leaves a moderate gap given there are no annotations to fill it.

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%, including the since_days/start_time mutual exclusion, so the baseline is 3. The description adds no meaning beyond the schema for count, since_days, or start_time.

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?

States a specific verb and resource ('Get recent tweets') plus a precise scope ('from accounts you follow (your home timeline)') and ordering ('newest first'), which implicitly separates it from search_tweets. It stops short of explicitly naming the sibling, so an agent must infer the distinction.

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

Usage Guidelines3/5

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

The scope phrase implies when to use it (personal feed of followed accounts) and it flags the paid-tier prerequisite, which is important selection context. There is no explicit when-not or named alternative such as search_tweets for keyword lookups.

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

Deploy Server