Skip to main content
Glama
jhartum

reddit-research-mcp

by jhartum

Reddit Pack

reddit_pack

Compile Reddit research on topics like opinions, bugs, fixes, or comparisons from selected subreddits with configurable depth and time.

Instructions

Build a compact Reddit research pack for opinions, bugs, fixes, comparisons, settings, alternatives, trends, guides, hardware, or general research.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoReddit search sort. Default relevance.
timeNoReddit time window. Default year.
depthNoHow much evidence to collect: quick, normal, deep. Default normal.
topicYesSearch topic, product, error string, repo URL/name, or comparison query.
intentNoResearch intent. Default general.
max_postsNoMaximum posts to return. Capped by depth.
subredditsNoOptional comma-separated subreddit names, for example: LocalLLaMA, LocalLLM, ClaudeCode. Do not pass a JSON list.
comments_per_postNoTop comments per fetched thread. Default depends on depth.
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry full behavioral burden. It mentions 'compact' but does not explain output size, performance constraints, or what happens internally. Lacks detail on how the pack is built.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single-sentence description is concise and front-loads the core verb ('Build') and resource ('compact Reddit research pack'). However, listing 10 intents inline clutters slightly; a bulleted list would improve scannability. Still, no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 8 parameters, no output schema, and no annotations, the description is too brief. It fails to explain what the 'pack' includes (e.g., summary, posts, comments) or how results are structured. Incomplete for the complexity involved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with descriptions for all parameters, so the schema does most of the work. The description adds no extra meaning beyond the schema (e.g., for 'depth' or 'intent'), so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it builds a compact Reddit research pack and lists specific intents (opinions, bugs, etc.). This distinguishes it from siblings like reddit_search or reddit_trends, though not explicitly. It is specific and actionable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs. alternatives such as reddit_search or reddit_thread. It does not clarify when not to use it or provide context for selecting among the intents.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jhartum/reddit-research-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server