Skip to main content
Glama

get_comments_by_id

Read-onlyIdempotent

Fetches Reddit comments by ID, including collapsed 'more replies' threads. Use it to expand specific comment chains when post context or source is known.

Instructions

Fetch specific comments by id (expands 'more replies collapsed').

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_ids": "<comment_ids>"
    },
    "name": "get_comments_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNoThe post these comments belong to (lets live reddit.com answer)
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_idsYesComment ids, t1_ optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, and openWorld, so the safety profile is covered. The description adds one genuine behavioral fact — that it expands 'more replies collapsed' stubs, i.e. you get fuller content than the collapsed marker — but says nothing about batch behavior, partial-miss handling, or the live/archive fallback consequence, despite 'openWorldHint' flagging external variability.

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?

One front-loaded sentence with zero filler, and the parenthetical is placed where it matters. The wording '(expands "more replies collapsed")' is slightly cryptic out of context, but it is dense with meaning rather than verbose.

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?

For a 3-parameter read tool with 100% schema coverage and no output schema, the description is adequate but thin: it never indicates the shape of the return (comment objects? bodies? parents?) or how objects missing from 'live' are surfaced from the archive. Those are the details an agent would still need to use the result 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%, so the baseline is 3; here the schema itself is unusually explanatory, documenting the live/archive/'auto' semantics and the optional t1_ prefix, and the description is consistent with it. The description adds no parameter meaning of its own beyond confirming id-based lookup, so it sits just at/above baseline rather than above it.

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 states a concrete verb ('Fetch') and resource ('comments') scoped by a specific selector ('by id'), which is enough to distinguish it from get_comment_thread (whole thread) and get_post (post-level). It stops short of naming any sibling explicitly, so an agent must infer the boundary.

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 by the name-plus-'by id' framing: call this when you already have comment ids in hand. There is no explicit when-not, no mention of what to use instead for a full thread or for discovering comments without ids, and no note about the source selection tradeoff the agent faces.

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