x-mcp

X timelines

x_timelines

Read-onlyIdempotent

Read X (Twitter) home and user timelines, mentions, liked posts, and bookmarks, with pagination plus start and end time filters.

Instructions

Read home and user timelines, mentions, liked posts and your bookmarks.

Actions (pass "action" plus that action's parameters):

home: Reverse-chronological home timeline for the authenticated account.
user: Timeline of posts authored by a user (1-100 per page).
mentions: Posts that mention a user (1-100 per page).
liked: Posts liked by a user, newest first (1-100 per page).
bookmarks: The authenticated account's bookmarks (1-100 per page).

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": {
      "action": "<action>"
    },
    "name": "x_timelines"
  }
}

Input Schema

Name	Required	Description
`action`	Yes	Action to perform. One of: home, user, mentions, liked, bookmarks.
`exclude`	No	Drop retweets and/or replies from the timeline.
`user_id`	No	Numeric X user id.
`end_time`	No	ISO 8601 timestamp. Exclusive upper bound.
`username`	No	X handle without the @ prefix.
`next_token`	No	Cursor from a previous response (meta.next_token).
`start_time`	No	ISO 8601 timestamp (e.g. 2026-01-31T12:00:00Z). Inclusive lower bound.
`max_results`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 7, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered; the description adds genuinely new behavior by disclosing ordering (reverse-chronological for home, newest-first for liked) and that bookmarks belong to the authenticated account. It stops short of stating auth requirements, rate limits, or that 'home' requires an authenticated user context.

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?

Front-loaded with a one-line summary followed by a clean per-action bulleted list, which is easy to scan and map to the action enum. Repeated '1-100 per page' on four bullets is redundant with the schema's max_results constraints and could be stated once.

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

Completeness4/5

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

For a five-action multiplexed read tool with no output schema, the description covers what each action returns conceptually and how to invoke it. The main remaining gap is per-action parameter applicability and the cursor/next_token continuation flow, which the agent must infer from the schema.

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 88%, so the baseline is 3 and the schema already carries parameter meaning. The description adds only the '1-100 per page' range which duplicates the schema's max_results bounds, and it does not clarify which parameters apply to which action — notably whether user_id, username, or exclude are required or meaningful for each action.

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?

States a specific verb ('Read') and enumerates the exact resources covered: home timeline, user timeline, mentions, liked posts, bookmarks. The action list makes it immediately distinguishable from siblings like x_posts and x_engagement without opening any schema.

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 description explains the calling convention (pass "action" plus that action's parameters) and gives one line of context per action, which implies usage. However, it offers no when-not guidance and never addresses overlap with siblings such as x_posts (authored posts) or x_engagement (liked content), leaving the agent to guess which tool to prefer.

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

Deploy Server