social-reddit-search
Search Reddit posts and comments across public subreddits.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Search Reddit posts and comments across public subreddits.
| Name | Required | Description | Default |
|---|---|---|---|
| payload | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
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. It states that only public subreddits are searched, but does not mention authentication requirements, rate limits, pagination, default sorting behavior, or what the results contain.
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 a single, front-loaded sentence with no wasted words. It is concise, though its brevity contributes to the lack of operational detail for a complex nested input schema.
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?
An output schema exists, so return values need not be explained. However, the input schema is nested and complex with zero property descriptions, and the tool description supplies no guidance on required parameters, filtering options, or behavioral limits, leaving the agent under-informed for correct invocation.
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 mentions no parameters at all. The nested payload includes queries, subreddits, sort, limit, timeframe, and other fields, but the description provides no semantic guidance for any of them.
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 states a specific verb ('Search') and resource ('Reddit posts and comments') with a scope ('across public subreddits'). It distinguishes the tool from general web search, but does not differentiate it from close siblings like social-reddit-community-research or social-reddit-voc-search.
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?
The description gives no explicit guidance on when to use this tool versus alternatives such as social-reddit-community-research or social-reddit-voc-search. Usage is only implied by the word 'Search' and the public-subreddit scope.
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.