Get detailed profile information for a Twitter/X user by username. Returns follower/following counts, bio, verification status, and account metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes | Twitter username (without @, max 50 characters) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden. It clearly indicates a read operation and lists the return fields, but does not cover error handling, auth requirements, rate limits, or behavior when a user is not found.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence that packs in the action, resource, and key output details. No unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter lookup tool, the description is adequate: it states what is returned and implies read-only behavior. It could be improved by noting error cases or that it only applies to Twitter/X usernames, but those are reasonably inferred. The absence of an output schema and annotations is offset by the explicit return list.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema covers the single parameter fully (100% coverage), including format ('without @') and length constraint. The description only redundantly says 'by username', adding no additional semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Get') and resource ('detailed profile information for a Twitter/X user'), and further distinguishes itself from siblings by listing concrete data points (follower/following counts, bio, verification status, account metadata).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied: if you need profile details for a username, this is the tool. However, it does not explicitly contrast with sibling tools like twitter_user_followers or twitter_user_tweets, nor does it mention any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly scoped by platform and resource (e.g. search_twitter vs twitter_user_tweets vs twitter_tweet_details). A few pairs like twitter_tweet_comments vs twitter_user_replies or facebook_page_posts vs search_facebook_posts could cause minor confusion, but descriptions generally clarify the distinction.
The dominant pattern is snake_case with a platform_prefix_resource suffix, and search_* consistently marks search operations. Minor deviations include noun-style names like amazon_best_sellers and place_photos, and the odd get_ skill/comments tools, but the overall convention is predictable.
74 tools is far beyond the typical well-scoped MCP server, even for a multi-platform API aggregator. The breadth is justified by the many platforms covered, but an agent will face a very large action space, and this could reasonably be split into per-platform servers.
The server provides strong lifecycle coverage for its read-only domain: search, profile/details, posts, and engagement data across most platforms. Gaps exist for some platforms (e.g. no LinkedIn person profile, no Facebook event details, no Truth Social profile/search, no Reddit subreddit-specific tools), but the core workflows are well covered.
