Skip to main content
Glama

reddit_deep_comment_search

Read-only

Get the actual Reddit comments containing your keyword, not just the posts. This tool expands comment trees and returns matched comments sorted by score, with body, author, and permalink.

Instructions

Genuine comment search: returns the ACTUAL comments whose body matches your keyword, sorted by score (highest first), with body, score, author, a comment-deep permalink, and the parent post. Unlike reddit_search_comments (which returns the parent posts, a Reddit limitation), this fetches each matching post's comment tree and filters the comment bodies for you, so you get first-hand opinions and answers directly. Premium call (it fans out into several reads): limit sets how many parent POSTS to expand, 1-25 (default 5), not how many comments come back. To go deeper than one call, paginate: pass the response's after cursor back as after to expand the NEXT batch of parent posts. max_comments optionally caps how many comments come back (the top-scored are kept). Matching is on the visible comment text at word boundaries (link URLs are ignored), so a result always mentions your query where a reader can see it. Best-effort: a deleted or deeply-nested comment may be missed (meta.truncated flags when a tree was too deep). Set group_by='author' for the research mode that returns WHO is talking about your query (distinct people ranked by matching-comment count) instead of a flat comment list, capped by max_authors. Example: q='best mechanical keyboard' sort='top'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query text. Supports Reddit search syntax (e.g. `subreddit:webdev`, `author:spez`, `"exact phrase"`, `title:...`).
tNoTime window that bounds which posts the search returns, e.g. 'week' = only posts from the past week. Unlike a subreddit listing, search applies this to the 'relevance' and 'top' sorts too. When omitted, Reddit defaults to 'all', so a broad 'relevance' query surfaces old high-upvote posts that only loosely match. Pass 'week' or 'month' to keep results recent and on-topic.
nsfwNoSet 'true' to include over-18 / NSFW results. Omit or 'false' to exclude them (default).
sortNoSort order for search. 'relevance' = best match (default), 'top' = highest score in the `t` window, 'new' = most recent, 'hot' = trending, 'comments' = most-discussed.
afterNoOpaque Reddit pagination cursor from the previous response's `after` field (a fullname like `t3_abc123`). Omit on the first call; pass it to fetch the next page.
limitNoNumber of parent POSTS to expand into their comment trees (1-25, default 5). Each is one upstream read, so higher = deeper coverage but slower and more expensive. To go past 25, paginate with `after`.
group_byNoSet to 'author' for the RESEARCH mode: instead of a flat comment list, return the distinct PEOPLE who mentioned your query, ranked by how many of their comments matched (then total score). Each author has comment_count, total_score, the subreddits they matched in, and their top comment. Omit for the normal comment list.
max_authorsNoOnly with group_by='author'. Optional cap on how many people are returned (the most prolific first). Omit to return everyone. meta.authors_capped is true when this trimmed the list.
max_commentsNoOptional cap on how many comments are returned; the highest-scored are kept. Omit to return every match. meta.capped is true when this trimmed the result.
Behavior5/5

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

Annotations already mark it as read-only and non-destructive, but the description goes beyond by disclosing that it is a 'premium call' that 'fans out into several reads', that matching is on visible comment text at word boundaries, and that results are 'best-effort' with meta.truncated flags. This is exactly the kind of context beyond standard annotations.

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?

The description is long but every sentence earns its place, covering purpose, differentiation, cost, pagination, limits, matching behavior, and research mode. It is front-loaded with the core purpose and each subsequent detail is necessary for correct usage of a complex tool.

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 must explain return fields and behavior, and it does: it lists returned fields (body, score, author, permalink, parent post), mentions meta.truncated for tree-depth issues, and describes group_by output (comment_count, total_score, subreddits, top comment). This makes the tool fully understandable without needing additional documentation.

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?

Though the schema already covers 100% of parameters, the description adds critical meaning: limit is clarified as expanding parent posts (not comment count), after is used for pagination, max_comments caps with top-scored kept, and group_by='author' changes the entire response shape. This significantly enriches understanding beyond the schema 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?

The description opens with 'Genuine comment search: returns the ACTUAL comments whose body matches your keyword', which is a specific verb+resource statement. It also explicitly distinguishes itself from the sibling tool reddit_search_comments by explaining the Reddit limitation, making its unique purpose unmistakable.

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 explicitly contrasts with reddit_search_comments ('Unlike reddit_search_comments... this fetches...'), telling the agent when to use this tool instead. It also provides practical usage guidance: setting limit, paginating with after, using group_by for research mode, and mentions premium cost.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/redditapis/redditapis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server