Skip to main content
Glama
TwitterAPIs

twitterapis

twitter_user_tweets

Read-only

Fetch a user's recent tweets with pagination, returning text, IDs, timestamps, and engagement metrics. Use cursor for next page and filter retweets/replies via flags.

Instructions

Get a user's recent posting timeline. IMPORTANT: this endpoint does NOT filter server-side, so the response routinely includes retweets and replies alongside original posts. Every item carries is_retweet, is_reply and is_quote booleans, so filter client-side on those flags if you need originals only, and read author.username rather than assuming every item was written by the requested user (a retweet's retweeted_tweet holds the original author). Returns tweet text, id, timestamp, and engagement metrics. Paginate with cursor to go further back. For the full back-catalogue in one call, use twitter_user_tweets_complete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMax items to return for this page. Typical range 1 to 200; endpoint default (20) applies if omitted. To page through results, pass the cursor from the previous response.
cursorNoOpaque pagination cursor from a previous response's next_cursor field. Omit on the first call; pass on subsequent calls to fetch the next page.
user_idNoNumeric Twitter/X user id (e.g. "44196397"). Provide exactly one of username or user_id.
usernameNoTwitter/X handle WITHOUT the leading @ (e.g. "elonmusk", "openai"). Provide exactly one of username or user_id.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Building on the annotations (readOnlyHint true, openWorldHint true), the description discloses critical behavioral details: no server-side filtering, inclusion of retweets/replies, presence of boolean flags, author.username nuance, return fields (text, id, timestamp, engagement metrics), and pagination. This substantially exceeds what annotations already provide.

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?

The description is efficiently structured: a concise purpose statement followed by a front-loaded critical caveat, return contents, pagination note, and an alternative tool reference. Every sentence serves a purpose with no filler.

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?

Given the absence of an output schema, the description thoroughly explains response contents (flags, author field, text, id, timestamp, engagement metrics) and pagination behavior, making the tool's behavior fully understandable for correct invocation. The mention of the complete alternative covers larger data needs.

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%, with each parameter fully described (count, cursor, user_id, username). The description adds no new parameter-level semantics beyond what the schema already states, though it mentions pagination via cursor. Baseline 3 is appropriate.

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?

The description clearly identifies the tool as retrieving a user's recent posting timeline, using specific language ('Get a user's recent posting timeline') that distinguishes it from sibling tools. It explicitly names an alternative for the full back-catalogue (twitter_user_tweets_complete), further clarifying its scope.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool vs alternatives, naming twitter_user_tweets_complete for full back-catalogue needs. It also explains client-side filtering for retweets/replies and pagination with cursor, giving clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TwitterAPIs/twitterapis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server