Skip to main content
Glama
Sign In
RedditAPIs

RedditAPIs

by redditapis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_post_comments

Read-only

Fetch a Reddit post and its full comment thread by permalink. Get post details, threaded replies, scores, and a cursor for pagination to read the complete discussion.

Instructions

Fetch a single post and its comment tree by permalink. Returns the post plus threaded comments (author, body, score, replies) and an after cursor. Use after finding a post via search/listing to read the full discussion. Pass the post's permalink from a prior result.

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": {
      "permalink": "<permalink>"
    },
    "name": "reddit_post_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
permalinkYesThe post permalink path from a prior post result, e.g. '/r/programming/comments/abc123/some_title/'. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.12

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, establishing the safety profile. The description augments this by disclosing the return format (post plus threaded comments with author, body, score, replies) and pagination via an 'after' cursor. It does not discuss rate limits or auth, but the provided context goes beyond annotation basics.

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?

Three sentences, front-loaded with the core purpose, followed by return details and usage context. No filler or redundancy; every sentence earns its place.

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

Completeness5/5

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

For a single-parameter read-only tool with no output schema, the description covers what it returns, the pagination cursor, and the proper triggering context. It is self-sufficient for an agent to select and invoke it correctly.

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 100% since 'permalink' has a clear description with an example. The description additionally tells the agent to 'Pass the post's permalink from a prior result,' which adds provenance guidance beyond the schema's static definition.

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 ('Fetch a single post and its comment tree by permalink') with specific resource and scope. It distinguishes itself from sibling tools like 'reddit_post' or 'reddit_search_comments' by specifying it returns the full comment tree, not just the post or search results.

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?

The description provides clear context for when to use the tool: 'Use after finding a post via search/listing to read the full discussion.' It implies a workflow but does not explicitly state when not to use it or mention alternative tools, so it falls short of the full 5.

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