Skip to main content
Glama
sadik004
by sadik004

reddit_browse_subreddit

Browse subreddit posts with sort options (hot, new, top, rising) and time filters to surface relevant content.

Instructions

Browse posts in a subreddit with sorting (hot, new, top, rising) and time filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNohot
limitNo
subredditYesSubreddit name (e.g. 'webscraping', 'Python')
time_filterNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the behavioral burden. It only says 'browse' and gives no information about authentication, read-only status, pagination, rate limits, or default behavior beyond the schema defaults.

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?

The description is one efficient, front-loaded sentence with no filler. It clearly communicates the core action and key options without wasting tokens.

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?

With no output schema and no annotations, the description is too thin to fully guide correct invocation. It omits return format, limit semantics, authentication context, pagination, and any behavior beyond the basic browsing action.

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 only 25%, and the description adds little beyond the schema's enum values. It names sorting and time filters but does not explain the limit parameter, the interaction between filters, or the meaning of time_filter values in context.

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?

The description states a specific verb ('Browse') and resource ('posts in a subreddit'), and adds distinguishing capabilities (sorting and time filters). It doesn't explicitly separate it from reddit_search or reddit_browse_user, but the subreddit scope makes the purpose clear.

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?

There is no guidance on when to use this tool instead of siblings like reddit_search or reddit_browse_user, nor any mention of when not to use it. Usage is only implied by the description's basic action.

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