Skip to main content
Glama
redditapis

RedditAPIs

by redditapis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_search

Read-only

Search Reddit posts by keyword across all communities or one subreddit, then filter by score, comments, and media to surface relevant discussions.

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 pagination cursor. Pass back the previous response's `after` value EXACTLY as it was returned; the format is not stable and a hand-written Reddit fullname loses the paging depth the cursor carries. Omit on the first call. When `after` comes back null there is no next page to request, and that does NOT reliably mean you have every item: Reddit often stops serving a busy listing long before it runs out. Read `listing_status` on that final response instead. It is `complete`, `truncated` or `unknown`, and ONLY `complete` means nothing is missing. Never report `truncated` or `unknown` to a user as the end of the data; say the answer is partial and widen across sorts, timeframes or search terms.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.3
    • changedInput schema / properties / after / description
      Previous value: -"Opaque 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."New value: +"Opaque pagination cursor. Pass back the previous response's `after` value EXACTLY as it was returned; the format is not stable and a hand-written Reddit fullname loses the paging depth the cursor carries. Omit on the first call. When `after` comes back null there is no next page to request, and that does NOT reliably mean you have every item: Reddit often stops serving a busy listing long before it runs out. Read `listing_status` on that final response instead. It is `complete`, `truncated` or `unknown`, and ONLY `complete` means nothing is missing. Never report `truncated` or `unknown` to a user as the end of the data; say the answer is partial and widen across sorts, timeframes or search terms."
  2. First observedv0.1.12

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds a non-obvious behavioral trait that the schema alone doesn't surface: filters are applied to the returned page rather than server-side, which is why a `meta` object with page-completeness counts is returned, and why you must paginate with `after` to filter more. That pre-empts a real misinterpretation of filtered results.

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, scope, and return shape, then usage, then the filtering caveat, then a compact example. Dense but every clause earns its place; the filtering/meta explanation is the only part that runs long, and it is warranted.

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 compensates by naming returned fields, the cursor, and the `meta`/page-completeness concept behind filtered results. For a 19-parameter read tool on an open-world source, that is sufficient for an agent to call it and interpret the response 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 the schema already carries full parameter meaning (enums, ranges, filter semantics, cursor guidance). The description only summarizes the filter families (min/max score, comment count, media type, post flags, re-sort), adding no syntax or default detail beyond what the schema provides. 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 ('Search Reddit posts') and immediately disambiguates scope ('across all of Reddit or within one subreddit'). It also enumerates what the result contains (author, score, comments, permalink, after cursor), letting an agent distinguish it from reddit_search_comments or reddit_search_communities 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete use cases ('topic/keyword research, brand monitoring, or finding discussions') and explains the scope selector ('Scope to a community with `subreddit`'). It stops short of naming the sibling search tools (comments, media, communities) as alternatives, so the when-not-to-use routing is left implicit.

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

Deploy Server

Other Tools