Skip to main content
Glama
vnnivas

Reddit MCP Server

by vnnivas

Search Reddit Posts

reddit_search_posts
Read-onlyIdempotent

Search Reddit posts by keyword to discover discussions, pain points, and competitor insights, with optional subreddit filtering.

Instructions

Search Reddit posts by keyword, optionally limited to a specific subreddit.

Use this to find discussions about specific topics, pain points, competitors, or industry signals across target communities.

Args:

  • query (string): Search terms (e.g., "compliance training outdated", "LMS video content")

  • subreddit (string, optional): Limit to one subreddit (e.g., "nursing"). Omit for all of Reddit.

  • sort (string): Sort by "relevance", "new", "hot", "top", "comments" (default: "relevance")

  • time (string): Time filter — "hour", "day", "week", "month", "year", "all" (default: "week")

  • limit (number): Max results 1-100 (default: 25)

  • response_format (string): "markdown" or "json" (default: "markdown")

Returns: Matching posts with titles, scores, comment counts, permalinks, and text previews.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort results by: relevance, new, hot, top, commentsrelevance
timeNoTime filter: hour, day, week, month, year, allweek
limitNoNumber of results (max 100)
queryYesSearch query (supports Reddit search syntax)
subredditNoLimit search to a specific subreddit (without r/ prefix). Omit to search all of Reddit.
response_formatNoOutput format: markdown or jsonmarkdown
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds value by specifying the return structure (titles, scores, comment counts, permalinks, text previews) and clarifying scoping behavior (omit subreddit for all Reddit), which goes beyond the structured safety annotations.

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?

The description is well-structured: purpose, usage context, args list, and return value summary. It is slightly repetitive with the schema (e.g., defaults and enums are repeated), but every sentence contributes info and there is no fluff.

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

Completeness5/5

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

With no output schema, the description covers return values explicitly. It addresses purpose, usage, parameters, and output, making the tool self-contained. For a search tool with moderate complexity, this is sufficient and complete.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description enhances parameters with concrete examples (e.g., 'compliance training outdated') and clarifies subreddit formatting (without r/ prefix), adding meaning beyond the schema definitions.

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

Purpose5/5

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

The description clearly states 'Search Reddit posts by keyword, optionally limited to a specific subreddit'—a specific verb and resource. It distinguishes itself from siblings like reddit_get_posts and reddit_get_comments by focusing on searching rather than direct retrieval.

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

Usage Guidelines4/5

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

Provides clear usage context: 'Use this to find discussions about specific topics, pain points, competitors, or industry signals across target communities.' However, it does not explicitly state when not to use it or mention alternatives, so it lacks exclusions.

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/vnnivas/reddit-mcp-server'

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