An MCP server that provides tools to browse and interact with Reddit, including searching posts, getting subreddit information, fetching comments, and retrieving user profiles.
The Reddit Browser MCP server defines 9 read-only tools with consistent verb_noun naming (search_reddit, get_subreddit_info, get_top_posts, etc.). All tools have descriptions and basic input schemas with type definitions. However, the implementation shows critical gaps: (1) Output schemas are completely undocumented, no return types, field lists, or structure guidance are visible in the source. (2) Parameter descriptions, while present, often lack specificity, many refer to 'default' or 'max' values without explaining what the tool actually returns or when to use it vs. alternatives. (3) Error handling is missing, no guidance on what happens on invalid input, rate limiting, or authentication failure. (4) No tool annotations (readOnlyHint, idempotentHint) despite all tools being read-only. (5) The descriptions are generic and do not mention prerequisites or use cases. Example: 'search_reddit' has a 3-sentence description but does not explain what fields are returned, how results are ranked, or what happens if no matches exist. Per-tool analysis: 6 tools score 55 - 65 (basic schema + weak description), 3 tools score 45 - 55 (schema present but minimal context). Average: 58.
Get hot posts from a subreddit
Get new posts from a subreddit
Get detailed information about a specific post including comments
Get information about a specific subreddit
Get top posts from a subreddit
Get currently trending subreddits
Get recent posts from a specific user
Get information about a Reddit user
Output schemas completely undocumented. No return type definitions, field lists, or structure guidance visible. Tools return Reddit API data but LLMs cannot determine what fields to expect or how to extract relevant data.
No tool annotations despite all 9 tools being read-only. Missing readOnlyHint/idempotentHint annotations prevents agents from safely reasoning about tool safety and retry semantics.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 50 | <=2025-11-25 | v2 |
Search Reddit for posts matching a query
Parameter descriptions lack specificity. Many describe 'default: X, max: Y' without explaining what data the tool returns or when to call it instead of similar tools. Example: 'limit': 'Number of results to return (default: 10, max: 100)' does not explain the ordering or what the results contain.
No error handling guidance. Source code shows authentication, rate limiting, and caching logic, but tools provide no descriptions of failure modes or recovery instructions. If Reddit API is down or rate-limited, LLM cannot determine what to do.
Inconsistent parameter naming. Some tools use 'limit' (search_reddit, get_top_posts), others imply pagination but do not expose offset/cursor. Agents cannot compose pagination uniformly across tools.
No documentation of what fields are returned by each tool. Agents cannot plan downstream calls or extract relevant data without trial-and-error. Example: does get_subreddit_info return subscriber count, rule list, or moderator list?