Skip to main content
Glama

X (Twitter) user timeline

x_posts
Read-only

Twitter API: User Tweets: the latest public tweets of one X (Twitter) account by handle or x.com URL, newest first. Per tweet the text, author handle and name, verification, followers, likes, replies, retweets, views, language, reply or quote parent, time and URL in the shared social schema; next_cursor gives the next page. Bad input is free; not found or no match is not charged. Price: $0.02 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "handle": "<handle>"
    },
    "name": "x_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNonext_cursor of the previous page.
handleYesAn X handle (with or without @) or an x.com profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses ordering (newest first), pagination semantics, and a full billing model: $0.02 per successful call over x402 with USDC on Base, bad input free, not-found uncharged. That payment requirement and the _meta["x402/payment"] channel are operationally essential and appear nowhere in the structured fields.

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 purpose, then returns, then paging, then pricing — a sensible order. The second sentence is a dense comma-list of returned fields and the pricing sentence is long, but no sentence is filler and all are load-bearing.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating the per-tweet fields in the shared social schema and explaining next_cursor, and it covers the payment prerequisite. Nothing an agent needs to call this correctly — input format, paging, cost, payment channel — is missing.

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 coverage is 100% and both parameters are already documented (handle accepts @ or x.com URL; cursor is the prior next_cursor). The description only reinforces the handle formats and links cursor to paging, adding little meaning beyond the schema, so the baseline 3 applies.

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+resource: 'the latest public tweets of one X (Twitter) account by handle or x.com URL, newest first.' The 'one account' scoping distinguishes it from the timeline-less x_search and from x_profile (which returns profile data rather than tweets), so an agent can route without opening a schema.

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

Usage Guidelines4/5

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

The 'one account' scope plus 'newest first' clearly implies when to reach for this versus the search siblings, and the paging hint ('next_cursor gives the next page') tells the agent how to continue. It never names an alternative tool explicitly or states exclusions, so it stops short of a 5.

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.