Skip to main content
Glama
Sign In
reddit_mcp

reddit_mcp

by ajaaysrinivaas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_subreddit_posts

Fetch front-page posts from any subreddit to surface active discussions. Specify subreddit, category (hot, new, top, rising), and number of posts.

Instructions

Fetch the front-page posts of a subreddit to surface active discussions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subreddit": "<subreddit>"
    },
    "name": "get_subreddit_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
subredditYesThe subreddit name (e.g. "python", "MachineLearning")
categoryNoFeed type — "hot", "new", "top", or "rising"hot
limitNoNumber of posts to return (max 100)

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It only states it fetches posts, but does not mention whether it is read-only, authentication needs, rate limits, or any side effects. The term 'front-page' may conflict with the 'category' parameter that allows other feeds.

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?

One sentence, no redundancy, front-loaded with the core action. Every word contributes to understanding.

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?

Despite having an output schema, the description lacks completeness: it omits details about default behavior (front-page may imply 'hot' but category allows others), error cases, or pagination. With no annotations, more context is needed for an agent to use it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds no additional meaning beyond the schema; it does not elaborate on parameter usage or constraints.

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 uses a specific verb 'Fetch' and resource 'front-page posts of a subreddit' with a clear purpose 'to surface active discussions'. It distinguishes from siblings like search_subreddit (which searches across Reddit) and get_user_activity (user-specific).

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?

The description provides no guidance on when to use this tool versus alternatives, no when-not-to-use conditions, and no exclusions. It simply states what it does without any contextual use cases.

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

Deploy Server

Other Tools