Skip to main content
Glama

xflux_get_user_tweets

Fetch a public X/Twitter user timeline by handle to review recent posts or summarize a KOL's activity.

Instructions

Fetch a public X/Twitter user timeline via XFlux. Use when the user asks what someone posted lately, KOL latest tweets, or to summarize a handle's recent activity.

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": {
      "username": "<username>"
    },
    "name": "xflux_get_user_tweets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
usernameYesHandle without @

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description must carry the full behavioral burden. It does disclose one meaningful constraint – the timeline must be 'public' – which implies private/protected accounts are not retrievable, but it says nothing about auth requirements, rate limits, result ordering, pagination, or how the default limit behaves.

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?

Two tight sentences, with the core action front-loaded before the usage triggers. Minor filler remains ('via XFlux') and jargon ('KOL') that a non-domain agent may not resolve, but nothing is redundant.

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 low-complexity two-parameter read tool this is close to sufficient, but with no output schema the agent gets no hint of what a result contains or over what time window 'recent' spans. The description also does not mention the default/max result behavior that a caller should know before invoking.

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 description coverage is 100%, with both 'username' ('Handle without @') and 'limit' ('Max results (default 20)') documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource: fetch a public X/Twitter user timeline. 'User timeline' is distinguishable from xflux_search_tweets and xflux_get_tweet, but the description never names or contrasts those siblings, so the differentiation is only implied.

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?

Provides concrete triggering scenarios: 'what someone posted lately', 'KOL latest tweets', or summarizing a handle's recent activity. That is clear when-to-use guidance, but there is no statement of when NOT to use it or which sibling to pick for keyword search vs. single-tweet lookup.

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