Skip to main content
Glama
Talljack

MCP Server Trending

by Talljack

get_twitter_user_tweets

Retrieve tweets from a specific Twitter user by username. Optionally set the number of tweets and use cached data.

Instructions

Get tweets from a specific Twitter/X user. Use this to see what a specific person is tweeting about.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesTwitter username (without @). Examples: 'levelsio', 'elonmusk', 'naval'.
limitNoNumber of tweets to fetch.
use_cacheNoWhether to use cached data.
Behavior2/5

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

No annotations exist, so the description carries full burden. It only states the basic function and does not disclose any behavioral details like rate limits, error handling, or privacy considerations.

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 short, two sentences, and directly conveys the tool's purpose without any unnecessary words.

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 simple read tool with three parameters and no output schema, the description is adequate. It covers the essential purpose and usage, though it could mention if results are ordered or paginated.

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 description adds minimal value beyond the schema's parameter descriptions. It provides examples for username but that's expected.

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 retrieves tweets from a specific user, distinguishing it from sibling tools like get_twitter_hashtag_tweets which fetch by hashtag.

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?

The description explicitly says 'Use this to see what a specific person is tweeting about', providing clear context for when to use it, though it does not mention when not to use or recommend alternatives.

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/Talljack/mcp_server_trending'

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