Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Browse a subreddit

browse_subreddit
Read-onlyIdempotent

List a subreddit's hot, new, top, rising, or controversial posts by time window, combine multiple communities, and paginate results for Reddit research.

Instructions

List a subreddit's posts: hot, new, top, rising or controversial.

Use listing="top" with time="year" or "all" to find a community's most valued posts, and "new" for the latest. Combine communities with "a+b" (at most 50) to read several in one call. To look for a topic inside a community, use search_reddit(subreddit=...) instead. Each result starts with [id] for get_post / get_posts. Output is capped near 50,000 characters; the last line gives the cursor for the next page.

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": "browse_subreddit"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoTime window; applies to top and controversial only.week
afterNoCursor from a previous 'next: after=...' line.
limitNoPosts per page, 1 to 100.
listingNohot (default), new (latest), top (most upvoted in `time`), rising (gaining votes now) or controversial (divided votes in `time`).hot
subredditYesSubreddit name ("dataengineering", "r/x" is fine) or several joined with + ("a+b").
body_charsNoCharacters of each post body to show, 0 to 4000.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare a safe, idempotent, open-world read, so the description is free to add operational behavior — and it does: results are prefixed with [id] for get_post/get_posts, output is capped near 50,000 characters, and the last line carries the next-page cursor. It also discloses that NSFW items are hidden by default and counted, and that a server setting can override include_nsfw=true.

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?

Four dense sentences, front-loaded with purpose then routing advice then output contract; every clause carries information an agent would otherwise have to discover by trial. No filler or restatement of the title.

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?

No output schema exists, yet the description still explains the return shape (id prefixes, character cap, cursor line) and the NSFW visibility caveat. Combined with full schema coverage and a complete annotation set, an agent has everything needed to call and paginate correctly.

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, but the description adds cross-parameter meaning beyond the schema: pairing listing="top" with time="year"/"all", and the "at most 50" cap on "a+b" community combinations, which the schema does not state. Remaining params (limit, body_chars, after) are left entirely to 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 ("List a subreddit's posts") and enumerates the five listing modes, so the agent knows exactly what it retrieves. It also names the sibling it is not (search_reddit) for in-community topic lookups, making it distinguishable without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance: listing="top" with time="year"/"all" for most valued posts, "new" for latest, and "a+b" to combine communities. It states the exclusion clearly — to search a topic inside a community, use search_reddit(subreddit=...) instead.

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