Skip to main content
Glama
Sign In
reddirect

reddirect

by jeebus87
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Browse Subreddit

browse_subreddit

Browse posts from any subreddit using sort options like hot, new, top, rising, or controversial. Filter by time range for top and controversial results.

Instructions

Browse posts from a subreddit with sort options (hot, new, top, rising, controversial). For top and controversial, you can specify a time range.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "subreddit": "<subreddit>"
    },
    "name": "browse_subreddit"
  }
}

Input Schema

NameRequiredDescriptionDefault
subredditYesSubreddit name without r/ prefix
sortNoSort order for postshot
timeNoTime range filter (only for top and controversial)
limitNoNumber of posts to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention read-only nature, authentication requirements, rate limits, or error handling. Only parameter behavior (sort/time link) is hinted, leaving significant gaps.

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 sentences, no redundancy, essential information front-loaded. Every word earns its place. Highly efficient.

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

Completeness3/5

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

The description covers main purpose and parameter dependency but omits details about return structure, pagination behavior (limit parameter described), and edge cases. For a simple listing tool with no output schema, it is minimally adequate but not comprehensive.

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?

Input schema has 100% coverage with clear parameter descriptions. The description adds minor value by explicitly noting that time range is only for 'top' and 'controversial', but this is already inferable from the schema's enum and description. Baseline 3 is appropriate.

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 the action ('browse posts'), the resource ('from a subreddit'), and the available options (sort orders, time range). It effectively distinguishes from sibling tools like get_post (specific post) and search_reddit (search across Reddit).

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?

No explicit guidance on when to use this tool versus alternatives like get_subreddit_info or search_reddit. The description implies usage for browsing posts with sorting but does not provide exclusions or comparative context.

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