Skip to main content
Glama

reddit_search

Read-onlyIdempotent

Search public Reddit posts by query, subreddit, sort order, and time range to find relevant discussions and community insights. OAuth optional for public reads.

Instructions

Search public Reddit posts. OAuth is optional for public reads.

Input Schema

NameRequiredDescriptionDefault
qNoSearch query alias
tNohour, day, week, month, year, all
sortNorelevance, hot, top, new, or comments
afterNo
limitNoResults to return
queryNoSearch query
subredditNoLimit to a subreddit
access_tokenNoOptional Reddit OAuth bearer token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.1.11
    • addedInput schema / properties / access_token / description
      Added value: +"Optional Reddit OAuth bearer token"
    • addedInput schema / properties / after
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / limit / description
      Added value: +"Results to return"
    • addedInput schema / properties / q / description
      Added value: +"Search query alias"
    • addedInput schema / properties / query
      Added value: +{
      +  "description": "Search query",
      +  "type": "string"
      +}
    • addedInput schema / properties / sort / description
      Added value: +"relevance, hot, top, new, or comments"
    • addedInput schema / properties / subreddit / description
      Added value: +"Limit to a subreddit"
    • addedInput schema / properties / t
      Added value: +{
      +  "description": "hour, day, week, month, year, all",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "access_token",
      -  "q"
      -]New value: +[]
  2. Addedv0.1.5

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's one real contribution is that OAuth is optional for public reads, which is useful auth context but leaves the relationship between the q and query parameters and any rate-limit behavior unaddressed.

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?

Two short sentences with the core purpose front-loaded and no padding. It is efficient, though arguably too terse for an 8-parameter search tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 optional parameters and no output schema, the description says nothing about pagination via after/limit, time filtering, sort options, or subreddit scoping. It is under-specified for an agent trying to construct a useful query without reading the whole 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 88%, so the schema already documents time range, sort, subreddit, limit, after and access_token. The description adds no parameter meaning, and in particular does not clarify the duplicate q/query aliases.

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?

Names a specific verb and resource ("Search public Reddit posts"), which cleanly separates it from reddit_read, reddit_post, reddit_comment and other Reddit siblings. It does not explicitly say how it differs from reddit_read, but the search framing is clear enough.

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

Usage Guidelines2/5

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

No statement of when to use this versus reddit_read or reddit_thread, and no exclusions. The only directive is that OAuth is optional for public reads, which is about auth, not tool selection.

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