Skip to main content
Glama
vnnivas

Reddit MCP Server

by vnnivas

Get Subreddit Posts

reddit_get_posts
Read-onlyIdempotent

Retrieve subreddit posts sorted by hot, new, top, or rising, with time filters, to monitor community discussions and identify engagement opportunities.

Instructions

Fetch posts from a specific subreddit sorted by hot, new, top, or rising.

Use this to monitor target communities for recent discussions, pain points, and engagement opportunities.

Args:

  • subreddit (string): Subreddit name without r/ prefix (e.g., "nursing", "instructionaldesign")

  • sort (string): Sort order — "hot", "new", "top", "rising" (default: "hot")

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

  • limit (number): Number of posts (1-100, default: 25)

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

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: hot, new, top, risinghot
timeNoTime filter for 'top' sort: hour, day, week, month, year, allweek
limitNoNumber of posts to return (max 100)
subredditYesSubreddit name without the r/ prefix (e.g., 'nursing')
response_formatNoOutput format: markdown or jsonmarkdown
Behavior3/5

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

Annotations already declare this as a safe read-only, idempotent operation. The description adds the return structure (titles, scores, comment counts, permalinks, text previews) but doesn't disclose any additional behavioral traits like rate limits or error handling. With high annotation coverage, this is acceptable but not exceptional.

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 with a purpose statement, usage note, Arg list, and return summary. It is front-loaded and readable, though the Args section somewhat duplicates the schema, making it slightly longer than necessary.

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

Completeness4/5

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

For a read-only tool with no output schema, the description covers purpose, usage, parameters, defaults, and return fields. It is sufficient for an agent to decide when and how to invoke it, though it omits explicit differentiation from siblings and edge-case handling.

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?

Schema coverage is 100%, so the baseline is 3. The description restates parameter details but adds minimal new semantics—only example subreddit names. It does not clarify semantics beyond what the schema already provides.

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 fetches posts from a specific subreddit with sort options (hot, new, top, rising). While it doesn't explicitly name sibling alternatives, the 'from a specific subreddit' phrase differentiates it from search or comment tools, but not as strongly as naming alternatives.

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?

The description says 'Use this to monitor target communities for recent discussions, pain points, and engagement opportunities,' which provides clear context for when to use. It does not explicitly mention when not to use it or point to siblings, so it falls short of the top score.

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