Skip to main content
Glama

twitter: Recent posts from an account

twitter_userTweets
Read-only

Recent posts from an account. An account's public posts with media, likes, replies and retweets: its pinned post and latest few, followed by a selection of older posts chosen by X, newest first. viewCount is null on the selection, and it is not a complete history. Costs 1 credit.

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": "twitter_userTweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoPosts to return, 5-100. Defaults to 20 on the official API and to every post available otherwise.
cursorNo`pagination.cursor` from a previous response. Official API only.
handleYesHandle (@jack), or a full x.com profile URL
cache_max_ageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / count / description
      Previous value: -"Posts to return, 5-100. Defaults to 20 on the official API and to every post on the page otherwise."New value: +"Posts to return, 5-100. Defaults to 20 on the official API and to every post available otherwise."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Adds real context beyond the readOnlyHint/openWorldHint annotations: the 1-credit cost, the fact that viewCount is null on the X-selected portion, and the explicit warning that results are not a complete history. Ordering (newest first) and the pinned-post behavior are also disclosed. Missing only pagination/rate-limit behavior, which the cursor schema partially covers.

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 compact sentences, front-loaded with the purpose followed by composition and then caveats plus cost. Minor redundancy between 'Recent posts from an account' and 'An account's public posts', but nothing wasted overall.

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

Completeness4/5

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

For a read-only, open-world listing tool with no output schema, the description covers what comes back (media, likes, replies, retweets, null viewCount), ordering, incompleteness, and cost. Only cache_max_age and the count/credit relationship remain unexplained.

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 75%, so the schema already documents handle, count and cursor well; the description adds no further syntax or defaults. cache_max_age has no description in either place, and the description does not connect credit cost to the count parameter, leaving that relationship to inference.

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?

Names a specific resource and operation ('public posts from an account') and characterizes exactly what the payload contains: pinned post, latest few, plus an X-selected set, newest first. It does not differentiate from nearby siblings such as twitter_profile or twitter_tweet, so an agent must infer the boundary rather than being told.

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 implied by the description of contents and the 'not a complete history' caveat, which tells the agent this is not a substitute for exhaustive retrieval. However, no sibling is named and there is no explicit statement of when to prefer twitter_profile, twitter_tweet, or twitter_communityTweets, or of any prerequisites.

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.