get_subreddit_searchSubreddit Search Group: Subreddit. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| t | No | ||
| show | No | ||
| sort | No | ||
| type | No | ||
| after | No | ||
| count | No | ||
| limit | No | ||
| before | No | ||
| category | No | ||
| sr_detail | No | ||
| subreddit | No | ||
| restrict_sr | No | ||
| include_facets | 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?
With no annotations, the description carries the full burden of behavioral disclosure. It only mentions billing, not side effects, required permissions, or any operational behavior. Agents cannot infer whether this is a read or write operation, what it returns, or any constraints.
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?
While the description is short, this is under-specification rather than conciseness. It contains no functional content and merely restates the tool name, making it a tautology with no earned sentences.
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?
Given the tool's complexity (14 parameters, no output schema, no annotations), the description is critically inadequate. It fails to explain any aspect of the tool's functionality, leaving the agent completely uninformed.
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 provides no parameter explanations. The 14 parameters (q, t, show, etc.) are completely undocumented in both the schema and the description, leaving the agent unable to construct valid calls.
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 'Subreddit Search Group: Subreddit. Billing per call: 1 Credits.' essentially repeats the title and adds billing metadata. It does not state what the tool does, lacks a verb+resource structure, and fails to distinguish it from numerous sibling tools like get_search or get_subreddit_posts.
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 guidance is provided on when to use this tool versus alternatives. There are over 20 sibling tools with overlapping names (e.g., get_search, get_subreddit_posts, get_subreddit_about), but the description gives zero context about appropriate 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.