Skip to main content
Glama

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

x_user_last_tweets

Get user's latest tweets. Latest tweets of a user, newest first. The list is inside data.tweets. Pass either userName or userId. 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_last_tweets"
  }
}

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`.
userNameNoScreen name without the @, e.g. `NASA`.
includeRepliesNoInclude replies (`true` / `false`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it usefully discloses newest-first ordering, pagination via cursor/next_cursor, and that results sit under data.tweets. It does not disclose authentication or rate-limit considerations, what 'latest' means in count or time window, or how replies are handled by default, leaving material behavior unstated.

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 definition is short and front-loads the core action and ordering. The first two sentences partly repeat each other ('latest tweets' twice), but the remaining sentences are useful and there is no significant bloat.

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 read-only retrieval tool with four schema-documented parameters and no annotations, the description covers ordering, pagination, one-of user identification, and the response location. However, with no output schema it gives only the top-level location of results and does not characterize the returned tweet objects, and it omits auth/rate-limit context, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaningful semantics by saying 'Pass either userName or userId,' clarifying a one-of requirement that the schema's both-optional fields do not state. Other parameter details it gives, such as cursor/next_cursor, are already documented in 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 uses a specific verb-resource pair ('Get user's latest tweets') and adds scope ('newest first'), so an agent knows it retrieves a user's recent tweets rather than generic search. It does not name or distinguish sibling tools such as timeline or mentions endpoints, so it stops short of full sibling differentiation.

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?

It implies the tool is for fetching a user's latest tweets, but gives no when-to-use versus when-not-to-use guidance and names no alternative tools. The only selection advice is 'Pass either userName or userId,' which is parameter selection, not tool selection.

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