get_subreddit_postsSubreddit Posts Group: Subreddit Posts. Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | ||
| t | No | ||
| show | 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?
The only extra information is 'Billing per call: 1 Credits,' which is a cost detail, not behavioral disclosure. With no annotations provided, the description must explain what the tool does, its side effects, or return behavior, but it does none of that.
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 wastes words repeating the title and adding a billing note. It fails to provide any substantive content, so it is under-specified rather than concise.
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 has 13 parameters, zero schema coverage, no annotations, and no output schema, the description is grossly inadequate. It provides no information to help an agent understand what the operation does or how to invoke it correctly.
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. All 13 parameters (q, t, show, type, after, count, limit, before, category, sr_detail, subreddit, restrict_sr, include_facets) are undocumented, leaving the agent with no semantic guidance.
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 is 'Subreddit Posts Group: Subreddit Posts.' which merely restates the tool name/title. It uses no verb indicating an action, no resource beyond the name, and doesn't distinguish from sibling tools like get_subreddit_new or get_subreddit_top.
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?
There is no guidance on when to use this tool versus alternatives. No context, no exclusions, no mention of suitable 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.