Skip to main content
Glama

reddit_query

Query stored Reddit items by profile, subreddit, pain score, or keyword. Filter and sort results to find unmet needs from collected data.

Instructions

Query already-stored items (no network).

Filters: profile (which sweep collected it), subreddit, min_pain (lower bound on the deterministic pain score), contains (case-insensitive substring over title+body). sort is one of pain|score|new|comments. Returns hydrated item dicts including their matched lexicon patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNopain
limitNo
profileNo
containsNo
min_painNo
subredditNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes return format ('hydrated item dicts including matched lexicon patterns') and behavior (querying stored items). No annotations exist, so description carries full burden; it covers read-only behavior and data retrieval.

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?

Highly concise: one sentence for purpose, one for filters/sort, one for return type. Uses backticks for parameters, making it scannable. No unnecessary words.

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?

Covers input parameters and return type adequately. Output schema exists to detail return values. Lacks error handling or performance notes, but reasonable for a query tool given sibling context.

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 0% (no descriptions in schema), but the description explains each parameter (profile, subreddit, min_pain, contains, sort) with specific meanings and allowed values. Only limit lacks description, but default of 50 is implied.

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?

Clearly states it queries already-stored items with no network involvement, lists specific filters and sort options. Distinguishes itself from sibling tools like reddit_fetch_thread and reddit_search that involve network calls.

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?

Explicitly notes 'no network' to indicate local queries. Lists available filters and sort parameters, guiding usage. Lacks explicit comparison to alternatives or when not to use, but context from siblings helps.

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