Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Read many posts at once

get_posts
Read-onlyIdempotent

Fetch full headers and bodies for up to 100 Reddit posts per request after a search, without comments, so you can read promising hits before opening threads.

Instructions

Fetch full headers and bodies of many posts in one request per 100 ids (no comments).

Use it after a search to read the complete text of the promising hits, then open the best threads with get_post for their comments. Missing or deleted posts are listed; entries that are not post ids or links are skipped and listed; posts that do not fit the budget are listed for a follow-up call.

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": {
      "posts": "<posts>"
    },
    "name": "get_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsYesPost ids, t3_ fullnames or URLs (list, or comma separated). Up to 300.
max_charsNoResponse budget in characters, 2000 to 200000.
body_charsNoBody characters per post, 0 to 40000.
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.8/5.0
Behavior5/5

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

Annotations already cover readOnly/idempotent/non-destructive, yet the description adds real behavior: requests are chunked at 100 ids, comments are never included, and missing/deleted/invalid/budget-excluded posts are surfaced as separate lists rather than silently dropped. That partial-result reporting is exactly the kind of detail an agent cannot infer from the structured fields.

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?

Two short blocks, front-loaded with what is fetched and what is excluded, followed by the workflow and then the edge-case handling. No filler sentences; the semicolon-separated clauses each carry distinct information.

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 no output schema, the description carries the return-shape burden, and it does explain that results are headers plus truncated bodies with lists of missing/skipped/over-budget items. It stops short of describing ordering, the shape of those lists, or how truncation is signaled per post, which keeps it from a 5.

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, and the description still earns a nudge by tying the 'budget' concept to max_chars behavior (posts that do not fit are listed for a follow-up call) and clarifying that non-id entries are skipped rather than erroring. It does not elaborate on body_chars or include_nsfw, but those are fully documented in 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?

The first sentence gives a specific verb (fetch), a specific resource (many posts), the payload returned (full headers and bodies) and an explicit exclusion (no comments). It also implicitly separates this batch reader from the single-thread get_post reader named later in the text.

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?

It prescribes a concrete workflow: call after a search to read promising hits, then use get_post on the best threads to get comments. Both the when-to-use and the alternative with its selecting condition are stated outright.

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