Skip to main content
Glama
X Use

X Use

by felixlark

Read a user's recent posts

x_user_posts
Read-onlyIdempotent

Read posts authored by an X user by username or numeric ID, with filters to exclude replies and retweets and to bound results by time or post ID.

Instructions

Read posts authored by an X user. The username is resolved to a user ID first when needed. Read-only.

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": {
      "user": "<user>"
    },
    "name": "x_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUsername with optional @, or numeric user ID.
excludeNoExclude replies and/or retweets.
end_timeNoRFC 3339 end time.
since_idNoReturn posts newer than this ID.
until_idNoReturn posts older than this ID.
expansionsNoX API expansions, for example author_id,attachments.media_keys,referenced_posts.
start_timeNoRFC 3339 start time.
max_resultsNoPage size accepted by GET /2/users/{id}/tweets.
poll_fieldsNoMapped to poll.fields.
post_fieldsNoMapped to the current query parameter post.fields.
user_fieldsNoMapped to user.fields.
media_fieldsNoMapped to media.fields.
place_fieldsNoMapped to place.fields.
pagination_tokenNoOpaque next_token from a previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so 'Read-only' is largely redundant. The one genuinely new behavioural fact is that the username is resolved to a user ID first, which implies an extra lookup and a possible resolution failure. Nothing is said about pagination, rate limits, or truncation of results.

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?

Three short sentences, front-loaded with the purpose before the operational detail. The trailing 'Read-only' sentence duplicates the annotations and could be dropped, but the overall text is tight with no filler.

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 14-parameter read tool with no output schema, the description is thin: it never describes what a returned post looks like, how paging works with pagination_token/max_results, or what happens on resolution failure. The schema compensates for parameter documentation, but return-shape and paging behaviour are left undocumented.

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%, so the schema already explains every parameter including exclude, time bounds, field expansions and pagination_token. The description only adds meaning for the 'user' parameter by clarifying that resolution happens automatically. Baseline 3 applies since the schema does the heavy lifting.

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 names a specific verb and resource ('Read posts authored by an X user') and adds a behavioural detail about identity resolution. It is clear enough to separate from a generic search tool, but it never names a sibling (x_search, x_thread, x_user) to sharpen the distinction.

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

Usage Guidelines3/5

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

Usage is only implied: 'read posts authored by an X user' suggests the per-user timeline case, and the resolution sentence hints the user arg accepts either form. There is no explicit when-to-use versus x_search or x_thread, and no stated prerequisites or exclusions when the user is not found.

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