Skip to main content
Glama

reddit_search

Read-only

Find Reddit discussions by keyword across all of Reddit or within one subreddit. Get matching posts with scores, comments, and permalinks for research, brand monitoring, or topic discovery.

Instructions

Search Reddit posts across all of Reddit or within one subreddit. Returns matching posts with author, score, comments, permalink, and an after cursor. Use for topic/keyword research, brand monitoring, or finding discussions. Scope to a community with subreddit. Optional advanced filters narrow the results by minimum/maximum score, comment count, media type, and post flags, with an optional re-sort of the page. Because filters are applied to the returned page, the response then carries a meta object with page-completeness counts, so a filtered result is never mistaken for the whole set; paginate with after to filter more. Example: q='rust vs go' sort='top' t='year'.

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.
limitNoMax items to return (1 to 100). The API clamps out-of-range values; endpoint default applies if omitted.
lockedNoFilter by the locked flag.
is_selfNotrue = only self/text posts, false = only link posts.
over_18NoFilter the page by NSFW flag (distinct from nsfw, which controls inclusion in the search).
spoilerNoFilter by the spoiler flag.
is_videoNotrue = only video posts, false = only non-video.
stickiedNoFilter by the stickied flag.
max_scoreNoKeep only posts with score <= this.
min_scoreNoKeep only posts with score >= this (applied to the returned page).
sort_typeNoRe-sort the filtered page (descending) by this field.
subredditNoOptional subreddit name (without r/) to restrict the search to one community. Omit to search all of Reddit.
contest_modeNoFilter by the contest_mode flag.
max_commentsNoKeep only posts with comment count <= this.
min_commentsNoKeep only posts with comment count >= this.
Behavior5/5

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

Beyond the annotations (readOnlyHint, destructiveHint), the description discloses a crucial behavioral trait: filters are applied to the returned page, not the search itself, with a `meta` object to indicate page completeness and a requirement to paginate for full filtering. This is non-obvious, decision-relevant context.

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 a well-structured paragraph that front-loads the purpose, covers use cases, explains the filtering caveat, and ends with a concrete example. Every sentence earns its place; no filler or redundancy.

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?

Despite 19 parameters and no output schema, the description provides sufficient orientation: return fields, pagination, the post-filtering caveat, subreddit scoping, and an example. The schema handles individual parameter details, so the description completes the high-level picture without gaps.

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. The description adds meaningful semantics by explaining the role of `subreddit`, grouping advanced filters, and showing an example with `q`, `sort`, and `t`. It reinforces how `after` enables pagination, adding value beyond 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 description opens with a specific verb and resource: 'Search Reddit posts across all of Reddit or within one subreddit.' It clearly distinguishes this tool from siblings like reddit_search_comments and reddit_search_communities by focusing on posts, and it enumerates the return fields (author, score, comments, permalink, after cursor).

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?

The description provides explicit use cases ('topic/keyword research, brand monitoring, or finding discussions') and explains how to scope to a subreddit. It doesn't explicitly name sibling alternatives for exclusion, but the scope and feature set clearly imply when this tool is appropriate.

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