Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Subreddit details, rules and wiki pages

get_subreddit_info
Read-onlyIdempotent

Describes a subreddit's size, age, type, description, rules, sidebar, and wiki pages so you can verify a community before trusting its advice and locate its FAQ.

Instructions

Describe a community: size, age, type, description, rules, sidebar and wiki pages.

Read this before trusting advice from a community, and to find its wiki (FAQ, recommended reading), which get_subreddit_wiki then reads. It does not list posts: use browse_subreddit for those. Costs up to 3 requests.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
include_rulesNoInclude the posting rules.
sidebar_charsNoSidebar characters to show, 0 to 50000.
include_sidebarNoInclude the sidebar text (often links and FAQs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive behavior, so the description focuses on what annotations cannot express. It adds a genuine cost budget ('Costs up to 3 requests'), which lets an agent plan call sequences. It stops short of describing truncation behavior for wiki/sidebar content or how many wiki pages are surfaced.

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?

Three short sentences, each doing distinct work: what it returns, why/when to call it, and what it does not do. No filler, and the most important content (the resource description) is front-loaded.

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 usefully enumerates the returned sections and ties wiki discovery to get_subreddit_wiki. Minor gaps remain: it does not say whether wiki pages are listed versus truncated, or that sidebar text is only included when include_sidebar is set, but an agent has enough to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so every parameter (include_nsfw, include_rules, sidebar_chars, include_sidebar) is already documented at the field level. The description adds no format or default guidance beyond the schema, so baseline 3 applies.

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 ('Describe a community') and enumerates exactly what is returned: size, age, type, description, rules, sidebar and wiki pages. It also explicitly contrasts with browse_subreddit for post listings, so an agent can distinguish it from siblings without opening a 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 concrete when-to-use conditions ('before trusting advice from a community', 'to find its wiki') and names the alternative for the excluded case ('does not list posts: use browse_subreddit for those'). It also names get_subreddit_wiki as the downstream consumer of the wiki links, which clarifies the intended workflow.

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