Search Reddit posts by query with optional filters for subreddit, timeframe, sorting, and pagination. Retrieve results for analysis or display.
Search posts across Reddit
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query | |
| t | No | Timeframe | |
| nsfw | No | true to include NSFW results | |
| sort | No | Sort order | |
| after | No | Pagination cursor from a previous response | |
| limit | No | Items to return, 1-100 | |
| subreddit | No | Restrict to a subreddit |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already tells the agent this is a safe read operation. The description adds only the resource scope ('posts') and does not disclose rate limits, pagination behavior, or result format. This is not a contradiction, but the description adds little behavioral context beyond the annotation.
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 zero wasted words. It immediately communicates the tool's purpose without restating schema details.
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 7-parameter search tool with no output schema, the one-sentence description is thin. It does not explain result shape, how the pagination cursor works, default sort/timeframe behavior, or how search syntax is interpreted. The schema covers parameter formats but not overall search semantics.
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 100%, with every parameter (q, t, nsfw, sort, after, limit, subreddit) already documented. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.
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 ('posts') with scope ('across Reddit'), and it distinguishes this tool from sibling search tools like get_search_comments, get_search_media, and get_search_users. An agent can tell exactly what resource this targets.
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 intended use is implied by the name and the phrase 'Search posts', and sibling names make the alternative search targets clear. However, the description does not explicitly state when to choose this tool over get_posts or other search variants, nor does it mention exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.