Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Read a subreddit wiki page

get_subreddit_wiki
Read-onlyIdempotent

Read or list a subreddit's wiki pages, such as FAQs and curated guides, to find community-vetted advice. Set a character limit to keep long pages within context.

Instructions

Read a subreddit wiki page (FAQs, guides, recommended tools), or list the pages.

Many technical communities keep their curated advice here. Pages come from get_subreddit_info or page="". Long pages are cut with a marker that gives the max_chars needed for the whole 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": "get_subreddit_wiki"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoWiki page, e.g. "index" or "faq". Empty lists the pages.index
max_charsNoCharacters to return, 500 to 200000.
subredditYesOne subreddit name.
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.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add operational detail — and it does, disclosing that long pages are truncated with a marker that reports the max_chars needed to retrieve the whole page. It leaves other behavior implicit, such as error handling for nonexistent pages or how listing output is shaped, but the truncation disclosure is genuinely useful context beyond the 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?

Three short sentences, front-loaded with the verb and resource, then usage rationale, then the truncation caveat. The middle sentence about technical communities is borderline padding but does earn its place by motivating usage; no restated parameter lists or boilerplate.

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?

No output schema exists, and the description covers the two things an agent most needs to know about returns: listing mode and truncation markers. Combined with 100% schema coverage on the four parameters and safety annotations, this is close to complete; only failure modes (missing page, private wiki) are unaddressed.

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 real meaning: it links max_chars to the truncation marker semantics, explaining that the cutoff marker tells the agent what value to set to fetch the full page. The page="" listing behavior is largely a restatement of the schema's own description, but the max_chars tie-in goes beyond structured fields.

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?

"Read a subreddit wiki page ... or list the pages" gives a specific verb plus resource and covers both operating modes (fetch a page vs. enumerate pages). It also names get_subreddit_info as the place page names come from, which separates it from siblings like browse_subreddit or get_posts that surface posts rather than curated wiki content.

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?

It supplies a clear reason to reach for this tool ("Many technical communities keep their curated advice here") and tells the agent how to enumerate pages with page="". No explicit when-not or named alternative for reading general subreddit metadata, so it stops short of full routing guidance.

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