Skip to main content
Glama
bestnite

reddit-readonly-mcp

by bestnite

Search Reddit

search_reddit
Read-only

Find Reddit posts, subreddits, or users by keyword and filter results by community, sort order, and time window. Use it to discover public discussions without an account or API key.

Instructions

Search Reddit posts (or subreddits/users via 'type'), optionally restricted to one subreddit. Read-only, anonymous. Returns {"data": [...], "after": cursor|null}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias of 'query' (Reddit's own parameter name). Provide either 'query' or 'q'.
sortNoSort: relevance (default), hot, top, new or comments.relevance
typeNoWhat to search for: link = posts (default), sr = subreddits, user = users.link
afterNoPagination cursor: the 'after' value returned by a previous call. Omit for the first page.
limitNoHow many items to return, 1-100 (default 10).
queryNoSearch terms; Reddit operators work ("exact phrase", author:name, self:yes, flair:x). Must be non-empty.
subredditNoRestrict results to this subreddit (without r/). Omit to search all of Reddit.
time_filterNoTime window: hour, day, week, month, year or all.all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description still adds real value by stating access is anonymous and by documenting the return shape ({data, after cursor}) and cursor-based pagination, which matters since no output schema exists. It omits rate-limit or auth-token context, keeping it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences with zero waste: purpose and scope first, then the read-only/anonymous property and return shape. Front-loaded and appropriately sized for an 8-parameter search tool.

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 8 params at full schema coverage and no output schema, the description supplies the missing return-shape and pagination context. The one gap is that it never says a query (or its 'q' alias) is effectively required for a meaningful search despite zero required params in the schema.

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 (q/query alias, sort, type, after, limit, subreddit, time_filter) is already documented inline. The description adds only the 'type' and subreddit framing already present in the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 extends scope to subreddits/users via the 'type' parameter, plus an optional subreddit restriction. An agent can distinguish it from browse_subreddit or get_top_posts by the search semantics, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage context is implied ('optionally restricted to one subreddit') but there is no explicit when-to-use/when-not guidance and no routing to alternatives like browse_subreddit for listing, or get_top_posts for rankings. An agent must infer selection from the 'type' enum alone.

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