Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Search Reddit posts

search_reddit
Read-onlyIdempotent

Search Reddit posts by title and body text using quoted terms, Boolean operators, subreddit filters, sorting, and pagination to locate relevant discussions and threads.

Instructions

Search Reddit posts by title and body text. Reddit's API cannot search comment text.

Unquoted multi-word queries are matched loosely and ranked by popularity, so dremio reflections tips returns unrelated posts. Use one to three specific terms, drop generic words (tips, best, help), and use the syntax Reddit supports: "dremio" quote a rare or exact term or phrase dremio AND iceberg require both terms subreddit:dataengineering only that community (or pass subreddit="a+b") -subreddit:jobboardsearch exclude a community (job-bot spam is common for product names) flair:Discussion title:benchmark selftext:kubernetes author:name site:github.com Each result starts with [id]: read one thread with get_post, or the full bodies of many results with get_posts. To find advice inside comments, open the most discussed threads (sort="comments") with get_post. 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": {
      "query": "<query>"
    },
    "name": "search_reddit"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance (default), top, new, hot, or comments (most discussed).relevance
timeNoTime window.all
afterNoCursor from a previous 'next: after=...' line, for the next page.
limitNoResults per page, 1 to 100.
queryYesSearch terms and operators (see the tool description).
subredditNoLimit to one subreddit ("dataengineering") or several ("a+b"). Empty = all of Reddit.
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.7/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the description correctly spends its words elsewhere: it discloses loose matching and popularity ranking (explaining why multi-word queries return junk), the ~50,000-character output cap, and the cursor on the last line. These are non-obvious traits an agent cannot learn from the schema or annotations.

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 purpose and the ranking caveat before the syntax block, and every operational line carries information. The example list is long (six syntax lines plus two routing sentences) but each entry is a distinct capability rather than filler.

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?

With eight parameters, no output schema, and a complex query language, the description supplies the syntax, the result format (each result starts with [id]), the size cap, and pagination via the trailing cursor. The only gap is that include_nsfw behavior and body_chars effects are only in the schema, which is a minor omission given full schema coverage.

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 baseline is 3, but the description adds real meaning the schema defers to it: the query operator syntax (quotes, AND, field prefixes), the 'a+b' multi-subreddit form, and sort="comments" as the most-discussed option. limit, body_chars, time and include_nsfw are left entirely to the schema, which is acceptable given its coverage.

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?

States a specific verb and resource ('Search Reddit posts'), immediately scopes it ('by title and body text'), and explicitly rules out comment search. That boundary plus the routing to get_post/get_posts makes it distinguishable from siblings like browse_subreddit or search_subreddits.

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 concrete when-to-use advice: one-to-three specific terms, drop generic words, quote rare terms, use subreddit:/flair:/author: operators, exclude job boards with -subreddit. It also routes to the right alternative for a different intent ('to find advice inside comments, open the most discussed threads (sort="comments") with get_post'), so both selection and non-selection conditions are covered.

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