Skip to main content
Glama

Reddit post comments

reddit_comments
Read-only

Reddit Post Comments: one Reddit post by id or URL with its comment thread (up to 3 reply levels, deleted and removed comments left out). Per comment the text, author, upvotes, parent, subreddit, time and permalink in the shared social schema; next_cursor gives more comments. Bad input is free; not found or no match is not charged. Price: $0.02 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "post": "<post>"
    },
    "name": "reddit_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesThe post: a Reddit post id (such as 1abc2de, or t3_1abc2de) or a reddit.com/r/<sub>/comments/<id>/, reddit.com/comments/<id> or redd.it/<id> URL.
cursorNonext_cursor of the previous page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses depth limiting (3 reply levels), filtering (deleted and removed comments excluded), pagination via next_cursor, and the per-comment field set. It also covers the commercial behavior: $0.02 per successful call, x402/USDC payment passed in _meta, and the fact that bad input and not-found are not charged.

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 content is dense and front-loaded: what is returned, then pagination, then pricing/payment. A few clauses are packed into one long sentence (fields, exclusions, cost, payment), but no sentence is pure filler.

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?

With no output schema, the description does the work of listing returned fields and pagination, which is exactly what an agent needs, and it discloses cost and the payment mechanism. The one gap is that 'the shared social schema' is never defined here, so the exact response shape remains slightly opaque.

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 100%, and the parameter descriptions already enumerate accepted id forms and URL shapes in more detail than the prose does. The description only restates 'by id or URL' and 'next_cursor gives more comments', adding no syntax beyond the schema, so the baseline 3 applies.

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 opens with a specific resource and scope: a single Reddit post by id or URL plus its comment thread. That clearly separates it from reddit_search (discovery) and youtube_comments (different platform), though it never names those siblings explicitly.

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?

Usage is implied rather than stated: the agent can infer this is for when it already has a post id or URL, and cursor is for paging. There is no explicit 'use X instead when...' routing against reddit_search, which is the most likely confusion in this sibling set.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.