Skip to main content
Glama

get_comment_thread

Read-onlyIdempotent

Retrieve a Reddit comment and its replies to inspect a discussion thread, with depth, sorting, and live or archive source controls.

Instructions

Get one comment and the replies under it (expands 'deeper replies').

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": {
      "comment_id": "<comment_id>"
    },
    "name": "get_comment_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNoPost id or URL, if known (saves a request)
sortNoReply orderbest
depthNoReply levels below the comment
limitNo
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
comment_idYesComment id (t1_ optional) or comment URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the useful behavioral detail that this expands a 'deeper replies' marker into a subtree, but says nothing about how the replies are returned (nested vs flattened), truncation, or the live-vs-archive behavior beyond what the schema's 'source' field already states.

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?

A single front-loaded sentence with no filler. It is slightly cryptic in isolation because 'deeper replies' is never defined as a marker coming from another tool's output, but nothing is wasted.

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?

With 6 parameters, no output schema, and a graph-like return (a comment plus descendant replies), the description should say what shape comes back and whether depth/limit truncate the tree. The schema covers the parameters, but return-shape expectations are left unstated.

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%, so the schema already documents post, sort, depth, limit, source, and comment_id well. The description adds no parameter meaning beyond that, 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?

States a specific verb and resource: retrieves one comment plus the replies beneath it, which is meaningfully more specific than the bare tool name. It does not, however, differentiate itself from the sibling 'get_comments_by_id', which an agent could plausibly confuse with this thread-expansion behavior.

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?

The clause '(expands "deeper replies")' is an indirect usage cue: call this when a prior result shows a 'deeper replies' placeholder. No explicit when-to-use/when-not rules and no mention of the get_comments_by_id alternative are given, so guidance is only implied.

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