search_reddit_users
Search Reddit users by keyword. Returns profile data including username, karma scores, account age, and bio.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search keyword (max 500 characters) |
API Direct
by io.apidirect
TDQS
A3.6/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosure. It states that profile data is returned (username, karma, account age, bio), but does not mention whether this is a read-only operation, rate limits, pagination, or any side effects. For a simple search tool, the basic return info is useful but not exhaustive.
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?
Two short sentences, front-loaded with the main purpose. No filler or redundancy; every word adds value.
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 one-parameter search tool, the description is fairly complete: it states the action, the target resource, and the returned fields. However, it lacks mentions of result limits, sorting, or potential ambiguity (singular vs. plural profiles), which would improve completeness.
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?
Input schema has 100% coverage: the 'query' parameter is described as 'Search keyword (max 500 characters)'. The description's 'by keyword' adds little beyond the schema. Baseline 3 applies because schema adequately documents the parameter.
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?
Description clearly states the action ('Search Reddit users by keyword') and the resource ('Reddit users'). It distinguishes from siblings like 'search_reddit' (posts) and 'search_reddit_comments' by specifically targeting user profiles, and lists return fields (username, karma, account age, bio) for additional clarity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives (e.g., search_reddit for posts, search_reddit_comments for comments). The description implies usage for finding Reddit users but does not mention any conditions, exclusions, or preferred scenarios.
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.
TDQS
B3.1/5.0
Disambiguation4/5
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.
Naming Consistency4/5
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.
Tool Count2/5
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.
Completeness4/5
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.