Skip to main content
Glama
reddit-research-mcp

reddit-research-mcp

Expand hidden comments

expand_comments
Read-onlyIdempotent

Fetch comments hidden behind get_post “[more: …]” stubs as reply trees, using comment IDs and returning new stubs or unfetched IDs for follow-up calls.

Instructions

Load the comments behind get_post's "[more: ...]" stubs, rendered as reply trees.

Up to 500 ids per call (100 per Reddit request, sent one at a time). New stubs found inside the expanded replies are listed the same way, so repeat until coverage is enough. Ids not fetched because of the budget are listed for the next call. A "[continue ...]" line is not an id list: open it with get_post(comment_id=...).

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": {
      "post": "<post>",
      "comment_ids": "<comment_ids>"
    },
    "name": "expand_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesThe post the comments belong to (id, fullname or URL).
sortNoUse the same sort as the get_post call that listed the ids.top
max_charsNoResponse budget in characters, 2000 to 200000.
comment_idsYesComment ids from the [more ...] lines of get_post output: a list, or one comma separated string. Up to 500 are fetched per call; the rest are listed for the next.
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
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description adds the throughput model (500 ids, 100 per upstream request, serial) and the budget/truncation behavior where leftover ids are listed for the next call. It does not state return-value structure in detail or any auth requirements, which keeps it just under a 5.

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, then budget mechanics, then the caveat about '[continue ...]' lines — each sentence carries new information. There is mild redundancy between 'Ids not fetched because of the budget are listed for the next call' and the schema's own wording about the 500 cap, keeping it from a perfect score.

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?

With no output schema, the description still conveys the response shape (reply trees, newly surfaced stubs listed the same way, remaining ids listed) so an agent knows how to drive a follow-up loop. For a budgeted, iteratively-called expansion tool this covers everything needed to call it correctly.

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

Parameters5/5

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

Schema coverage is already 100%, so the bar is what the prose adds: it explains the request batching (100 per Reddit request, sent one at a time) and clarifies that ids flagged as unfetched belong in the following call. It also warns that '[continue ...]' markers are not id lists, which directly prevents a malformed comment_ids argument.

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 ('Load the comments behind get_post's "[more: ...]" stubs') plus the output shape ('rendered as reply trees'). It explicitly names the sibling get_post whose output feeds it, so an agent can distinguish it from get_post without opening either 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/when-not routing: iterate 'repeat until coverage is enough', and the explicit exclusion that a '[continue ...]' line must be opened with get_post(comment_id=...) rather than passed here. That is a named alternative plus the condition that selects it, which is the top of the scale.

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