Skip to main content
Glama
ajaaysrinivaas

reddit_mcp

search_subreddit

Run targeted keyword searches within a specific subreddit to find relevant posts. Filter results by sort type and time window.

Instructions

Run highly targeted keyword searches within a specific subreddit community.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subredditYesThe subreddit name to search within (e.g. "saas", "entrepreneur")
queryYesSearch keywords
sortNoRanking — "relevance", "hot", "top", or "new"relevance
time_filterNoTime window — "day", "week", "month", "year", or "all"all
limitNoNumber of results to return (max 100)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states 'keyword search' without disclosing whether the operation is read-only, requires authentication, or has rate limits. The absence of such details leaves the agent underinformed about safety or side effects.

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

Conciseness5/5

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

The description is a single, clear sentence with no redundancy. It is front-loaded with the core action and resource, making it highly efficient for an agent to parse.

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

Completeness3/5

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 description omits details about search behavior (e.g., whether it matches titles, bodies, or both). Given the schema richness and sibling context, a middle score reflects adequate but not thorough completeness.

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?

The input schema already fully describes all 5 parameters (100% coverage). The description adds no extra meaning beyond what the schema provides, so a baseline score of 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 the tool's function: running targeted keyword searches within a specific subreddit. It uses a specific verb ('run... searches') and resource ('subreddit community'). While it distinguishes from listing-focused siblings like get_subreddit_posts, it doesn't explicitly contrast with them.

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 is provided on when to use this tool versus alternatives like get_subreddit_posts. The description only implies usage for keyword searches but offers no exclusions or context about prerequisites.

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/ajaaysrinivaas/reddit_mcp'

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