Read public posts from any Reddit subreddit, with sorting by hot, new, top, or rising and optional time filters. Use it to fetch subreddit content for analysis or monitoring.
Read public posts from a Reddit subreddit. OAuth is optional for public reads.
| Name | Required | Description | Default |
|---|---|---|---|
| t | No | hour, day, week, month, year, all | |
| sort | No | hot, new, top, rising | |
| after | No | ||
| limit | No | ||
| subreddit | Yes | ||
| access_token | No | Optional Reddit OAuth bearer token |
Changes observed during successful MCP inspections.
v0.1.11Input schema / properties / access_token / descriptionAdded value: +"Optional Reddit OAuth bearer token"Input schema / requiredPrevious value: -[
- "access_token",
- "subreddit"
-]New value: +[
+ "subreddit"
+]v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful auth context ('OAuth is optional for public reads'), which is a real behavioral detail beyond annotations. It does not describe rate limits, pagination, or what 'public' excludes, so this is a moderate addition rather than rich disclosure.
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?
Two short sentences with no filler. The main purpose is front-loaded, followed immediately by the only auth caveat. Every sentence earns its place.
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 6-parameter read tool with no output schema and only 50% schema description coverage, the description leaves important gaps: pagination via 'after', 'limit' behavior, default sorting, and time-window semantics are unexplained. An agent can attempt a basic call, but cannot confidently use the full parameter set from this definition alone.
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 50%: t, sort, and access_token have descriptions, but after, limit, and subreddit do not. The description only indirectly references subreddit and access_token, and says nothing about after, limit, sorting, or time filtering. It does not compensate for the undocumented parameters.
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 and resource: 'Read public posts from a Reddit subreddit.' That is clear and actionable. It does not explicitly distinguish this listing read from sibling tools like reddit_search or reddit_thread, so it falls short of a 5.
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 phrase 'Read public posts from a Reddit subreddit' implies the basic use case, and 'OAuth is optional for public reads' clarifies an auth prerequisite. However, there is no explicit guidance on when to use this tool versus reddit_search, reddit_thread, or reddit_user, so usage is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.