Skip to main content
Glama

browse_subreddit

Read-onlyIdempotent

List posts from a subreddit with sorting, time filters, pagination, and live or archive source selection for browsing discussions.

Instructions

List posts in a subreddit.

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
sortNoRanking. Default: hot on live, new on archive (archive has only new).
timeNoTime window for top/controversial.
limitNo
cursorNonext_cursor from a previous call
sourceNoData source. 'auto' tries live reddit.com (if a session cookie is configured) and falls back to the Arctic Shift archive; 'live' or 'archive' forces one.auto
subredditYesSubreddit name, with or without r/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description adds nothing beyond them: it does not explain that results are paginated with next_cursor, that 'auto' silently falls back to the archive when no live cookie is configured, or that the default sort changes with the source. For a tool with a non-obvious live/archive fallback, that is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six words, front-loaded, with zero filler — but the problem is under-allocation rather than verbosity. A single sentence is too small a budget for a six-parameter, paginated, dual-source listing 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?

With no output schema and six parameters including cursor-based pagination and a live/archive mode switch, the description leaves the agent to reconstruct behavior from field docs alone. It never says what a result contains, how to page through, or when archive results differ in ordering.

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 83%, and the schema already documents sort defaults, the time window's applicability to top/controversial, cursor as 'next_cursor from a previous call', and the source fallback. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'List' plus the resource 'posts in a subreddit' is clear enough to know what comes back at a high level, but it does nothing to distinguish this from siblings like search_posts, get_post, or get_comments_by_id. An agent must infer that this is the unfiltered enumeration tool rather than a search or single-item fetch.

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 when-to-use guidance at all: no mention of when to prefer browse_subreddit over search_posts, no note that pagination continues via cursor, and no statement of preconditions. The only hint of alternatives ('live' vs 'archive') lives in the schema, not the description.

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