reddit-mcp

Get a post with comments

reddit_get_post

Fetch a Reddit post and its comment tree using the post ID and subreddit. Choose comment sort order: best, top, new, controversial, or old.

Instructions

Fetch a post (submission) and its comment tree by post id (t3_... or bare id) or subreddit+id.

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>",
      "postId": "<postId>"
    },
    "name": "reddit_get_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes
`subreddit`	Yes
`commentSort`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, description carries full burden but only discloses two identification methods; lacks info on auth, rate limits, error behavior, or effect of invalid inputs. Not misleading but insufficient.

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?

Single, well-structured sentence front-loading the core purpose and identification options. No unnecessary words or repetition.

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?

Given 3 parameters, 0% schema coverage, no output schema, and no annotations, a single sentence is insufficient. Lacks guidance on return format, error cases, or pagination. Minimal yet functional.

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?

Adds meaning for postId (accepts t3_ prefix or bare) and subreddit (required when not using full ID). However, does not explain commentSort parameter (enum values are in schema but no added context). Partially compensates for 0% schema coverage.

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?

Clearly states verb 'Fetch' and resource 'post (submission) and its comment tree', distinguishing it from sibling tools that list or search posts. However, does not explicitly contrast with siblings like 'reddit_get_subreddit_posts'.

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

Usage Guidelines3/5

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

Implies usage when you have a post ID or subreddit+ID, but lacks explicit when-to-use vs. alternatives or when-not-to-use scenarios. No reference to sibling tools for comparison.

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

Deploy Server