Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Read a post and its comments

get_post
Read-onlyIdempotent

Read a Reddit post and its full comment tree in one request, including metadata, body text, and sortable replies. Use it to inspect a thread or expand hidden comments.

Instructions

Read one thread: the post and its comment tree in one request.

The header has id, subreddit, date, score, upvote ratio, comment count, flair, flags, link URL, poll options, gallery size, crosspost origin and the body (first 6,000 characters by default; body_chars changes that). Comments print as "[id] date score u/author (OP) (edited) [flair]" with replies indented. Reddit hides part of large threads behind "[more: N comments; ids: ...]" stubs; the last line reports coverage ("Shown X of Y comments...") and how many stubs are listed. Pass stub ids to expand_comments to read them. Use comment_sort="new" for the latest replies, "controversial" for disputes, "qa" for AMAs. A comment permalink opens the thread at that comment (add context=2 to see its parents); an id not in the post is an error.

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": {
      "post": "<post>"
    },
    "name": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost id (1abc234), t3_ fullname, reddit.com/old.reddit.com permalink, comment permalink, or redd.it link.
contextNoWith comment_id or a comment permalink: parent comments to show above it, 0 to 8.
max_charsNoResponse budget in characters, 2000 to 200000.
body_charsNoPost body characters to show, 0 to 40000, so long posts leave room for comments.
comment_idNoOpen the thread at this comment (id or t1_ fullname).
comment_sortNotop (default), confidence (Reddit's 'best'), new, controversial, old, qa (AMAs).top
include_nsfwNoShow posts, comments and communities Reddit marks NSFW (18+). Off by default; hidden items are counted in the output. A server setting can keep them hidden even when true.
comment_depthNoReply depth to load, 1 to 10.
comment_limitNoComments to load across all depths, 1 to 500.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, open-world). The description goes well beyond that: it describes the rendered header fields, body truncation at 6,000 chars, indented reply formatting, the "[more: N comments; ids: ...]" stub mechanism, the coverage summary line, and the error case for ids not in the post.

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?

Front-loaded with the core statement, then output shape, then routing advice. The header field enumeration is long but justified given there is no output schema; a few phrasings could be tightened but nothing is wasted.

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?

For a 9-parameter read tool with no output schema, the description supplies the missing return-value picture (header fields, comment line format, coverage/stub reporting) and the two relevant edge cases (stubs, invalid id). An agent has enough to invoke it correctly on the first try.

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 already 100%, so the baseline is 3, but the description earns above that by explaining body_chars as a tradeoff against comment room and by giving practical meaning to comment_sort values. It does not add much on context, max_chars, or comment_depth beyond the schema.

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?

Opens with a specific verb and resource: "Read one thread: the post and its comment tree in one request." That framing distinguishes it from the plural get_posts and from expand_comments, which is named later as the follow-on for hidden comments.

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?

Gives concrete routing guidance: pass stub ids to expand_comments, use comment_sort="new"/"controversial"/"qa" for particular needs, and add context=2 when opening at a comment permalink. It stops short of an explicit when-not-to-use statement (e.g., for multiple posts use get_posts), so it is clear but not fully exhaustive.

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