Skip to main content
Glama

CheapXAPI — Twitter (X) Search, Tweets, Profiles & Followers MCP Server

x_user_tweet_timeline

Get user's tweet timeline. Tweet timeline of a user by numeric user ID. The list is inside data.tweets. Paginated: use cursor / next_cursor.

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": "x_user_tweet_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor. Leave empty for the first page, then pass `next_cursor` from the previous response.
userIdNoNumeric user ID, e.g. `11348282`.
includeRepliesNoInclude replies (`true` / `false`).
includeParentTweetNoInclude the parent tweet of replies (`true` / `false`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and does disclose useful traits: it is a read-style "Get" operation, results are inside `data.tweets`, and pagination uses `cursor` / `next_cursor`. It does not cover rate limits, authentication requirements, sort order, or whether retweets are included, so important behavioral context is still missing.

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 short and front-loads the core purpose before pagination details. The second sentence largely restates the first, which is a minor redundancy but does not obscure the tool's function.

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 simple read operation with fully described parameters and no output schema, the description provides the key return-location detail (`data.tweets`) and pagination behavior. It is mostly complete, though additional context about default reply handling or result ordering would improve 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%, so all four parameters are already documented in the input schema, including defaults for replies and parent tweets. The description only restates the numeric user ID and pagination cursor, adding no meaningful parameter semantics beyond the schema.

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 states a specific verb and resource: "Get user's tweet timeline" for a numeric user ID. It is clear what the tool returns, but it does not explicitly differentiate this timeline from siblings such as x_user_last_tweets or x_user_mentions.

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?

The description explains pagination mechanics with `cursor` / `next_cursor`, but gives no guidance on when to choose this tool over sibling timeline or tweet-search tools. It lacks any when-not-to-use or alternative-selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources