get_subreddits_searchSearch Subreddits Group: Subreddit. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| show | No | ||
| sort | No | ||
| after | No | ||
| count | No | ||
| limit | No | ||
| before | No | ||
| sr_detail | No | ||
| show_users | No | ||
| search_query_id | No | ||
| typeahead_active | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only mentions billing ('Billing per call: 1 Credits') which is a minor detail, but provides no information about authentication requirements, rate limits, pagination behavior, or what the response contains for this search functionality.
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?
The description is short, but not effectively concise - it's under-specified. While 'Search Subreddits' is direct, the additional text about group and billing is low-value. The description doesn't earn its place by providing meaningful information to the agent.
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 search tool with 11 parameters, no annotations, no output schema, and a search-related sibling (get_subreddit_search), this description is severely incomplete. The agent cannot determine which parameters are important (like q for the query), what format values should take, or how results are returned.
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?
Schema description coverage is 0%, and the description adds no parameter context. There are 11 parameters with no documentation beyond their parameter names. The description doesn't compensate for the lack of schema information, leaving the agent to guess what many parameters like 'show', 'sr_detail', 'show_users', and 'typeahead_active' do.
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 'Search Subreddits' with the group 'Subreddit' gives a basic idea that this tool searches subreddits. However, it doesn't clearly distinguish itself from siblings like get_subreddit_search or get_subreddit_posts which could also perform searching.
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?
No usage guidelines are provided. The description doesn't mention when to use this tool versus alternatives like get_search, get_subreddit_search, or other sibling tools. There's no context about preferred use cases.
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.
Each tool targets a distinct resource and action combination (e.g., get_hot vs get_subreddit_hot vs get_user_posts). The scope is clearly delineated by prefixes like 'get_subreddit' and 'get_user', making it easy for an agent to pick the right tool.
All tools follow the consistent 'get_<resource>_<modifier>' pattern using snake_case. Even get_by_id fits the general get_ prefix style. The naming is uniform and predictable across 31 tools.
With 31 tools, the count exceeds the 25+ threshold considered too many. While Reddit has many read endpoints, this server covers only GET operations and still feels bloated, especially with multiple near-duplicate sort variants. It could be consolidated.
The tool surface is entirely read-only (only get_* operations). For a Reddit integration, obvious write operations like posting, commenting, voting, and moderation actions are missing. This creates significant gaps for many use cases and limits the server to exploration only.