Skip to main content
Glama

reddit_search

Search Reddit for a query and store matching posts. Optionally restrict to specific subreddits for targeted analysis.

Instructions

Search Reddit live for a query and store the matching posts.

If subreddits is given the search is restricted to each of them (results merged + de-duplicated); otherwise it is a site-wide search. Posts are stored so you can drill into them later with reddit_query / reddit_get_evidence / reddit_fetch_thread. Returns the stored posts as dicts (id, subreddit, author, score, permalink, title, body, ...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNorelevance
timeNoyear
limitNo
queryYes
subredditsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses that posts are stored and returns a dictionary with specified fields. However, it does not mention rate limits, auth requirements, or any side effects beyond storage. Given the read-like nature, this is adequate but not exhaustive.

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?

The description is concise with two well-structured sentences. It front-loads the purpose and then provides additional details on behavior. While it could be slightly more streamlined, it contains no unnecessary words and is easy to parse.

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?

Given the tool's complexity (5 params, output schema present), the description covers the core behavior, return value structure, and relationship to sibling tools. It explains storage and linking, and lists the return fields. No major gaps are apparent for an agent to effectively use the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all parameters. It only explains 'query' and 'subreddits', but fails to describe 'sort', 'time', and 'limit' which are present in the schema with defaults but no textual explanation. This leaves a significant gap for an agent to correctly use these parameters.

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 clearly states 'Search Reddit live for a query and store the matching posts', indicating a specific verb-resource combination. It distinguishes from siblings by explaining that results are stored for later use with other tools like reddit_query, and details the subreddit restriction behavior.

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?

The description explicitly tells when to use this tool (live search and store), and mentions alternatives for drilling into stored posts (reddit_query, reddit_get_evidence, reddit_fetch_thread). It also clarifies the search scope: restricted if subreddits given, site-wide otherwise.

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/011-sam-110/Prospector'

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