Skip to main content
Glama
kaitoInfra

twitterapi-io-mcp-server

get_user_last_tweets

Fetch the most recent tweets from a Twitter/X user. Use userName or userId to get tweets sorted by creation time, with an option to include replies.

Instructions

⚠️ ONLY for 'latest / recent / what's new' queries about a user. DO NOT use for date-range queries (e.g. 'tweets from January 2026', 'tweets last week', 'tweets between X and Y', 'tweets in 2025'). For specific dates / older tweets, use search_tweets with query like 'from:elonmusk since:2026-01-01 until:2026-02-01'.

Fetch the MOST RECENT tweets posted by a Twitter/X user, sorted by created_at descending (newest first). Provide EITHER userName (screen name, no @) OR userId (numeric). Use userId when known — handles can change. Set includeReplies=true to include the user's reply tweets in addition to top-level tweets. Paginates via cursor (~20 per page).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNameNoTwitter/X screen name without @ (e.g. 'elonmusk'). Provide EITHER userName OR userId.
userIdNoTwitter/X numeric user ID (e.g. '44196397'). Provide EITHER userName OR userId. Prefer userId if known — handles can change.
cursorNoPagination cursor; omit for first page.
includeRepliesNoInclude the user's reply tweets in addition to top-level tweets. Default false — only top-level tweets.
Behavior5/5

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

Despite no annotations, the description discloses key behaviors: sorting order, pagination (~20 per page, cursor-based), default for includeReplies, and the mutual exclusivity of userName/userId. This fully compensates for missing annotations.

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 written with a warning first, then core functionality, then specific parameter guidance. Every sentence adds value without redundancy.

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?

For a tool with 4 parameters, no annotations, and no output schema, the description provides all necessary information for selection and correct invocation: purpose, usage constraints, parameter behavior, pagination, and defaults. No gaps are evident.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds critical context: mutual exclusivity of userName/userId, cursor usage for pagination, and default behavior for includeReplies. This enhances understanding beyond the raw schema.

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 states the tool fetches the most recent tweets for a user, sorted by created_at descending. It explicitly contrasts with date-range queries and directs to a sibling tool search_tweets, making the purpose unambiguous.

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?

Provides explicit when-to-use (latest/recent queries) and when-not-to-use (date-range queries) with a concrete alternative and example. Also advises preferring userId over userName, aiding correct invocation.

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/kaitoInfra/twitterapi-io-mcp-server'

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