Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_comments_tree

Fetch an archived Reddit post's nested comment tree by ID, with bounded depth and breadth, including replies and collapsed branch markers for discussion analysis.

Instructions

Get an archived Reddit comment tree. Returns a bounded nested comment tree from Arctic Shift's public archive. t1 entries contain comments and their replies; more entries mark collapsed branches and include child ids/counts. Omitted parent_id requests the whole tree, while an explicitly empty parent_id requests top-level comments only. Empty archived trees return 200 with an empty comments array. Archived scores can lag changes for roughly 36 hours; slow or throttled upstream requests return 503 with Retry-After.

Input Schema

NameRequiredDescriptionDefault
idYesReddit post id or t3_ id
limitNoMaximum archive comment nodes to expand, defaults to 50 and clamps to 100
parent_idNoParent comment id; an explicitly empty value selects top-level comments
start_depthNoInitial depth, defaults to 3 and must be between 0 and 8
start_breadthNoInitial breadth, defaults to 2 and must be between 0 and 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it documents the return shape (`t1` comments with replies, `more` collapsed branches with child ids/counts), the empty-tree 200-with-empty-array case, a ~36 hour score-lag caveat, and 503 with Retry-After on throttling. These are exactly the edge cases and failure modes an agent needs.

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?

Front-loaded with the core action in the first sentence, followed by tightly packed sentences covering structure, parameter edge-casing, empty results, and latency/error behavior. No filler; each sentence contributes distinct information.

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 tool with no output schema and no annotations, the description provides return structure, edge cases, and upstream error/latency behavior, while all five parameters are covered by the 100% schema. An agent has everything needed to invoke and interpret it.

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 baseline would be 3, but the description adds genuine semantics beyond the schema: it clarifies that an omitted parent_id requests the whole tree while an explicitly empty one requests top-level comments only, a distinction the schema does not fully spell out. The `more`/`t1` structure also gives downstream meaning to the limit/expansion parameters.

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 ('Get') and resource ('archived Reddit comment tree') and elaborates the bounded nested tree structure, so the agent knows exactly what it retrieves. It does not explicitly distinguish itself from siblings like reddit_archive_comments_ids or reddit_archive_comments_search, so it falls short of the 5 bar.

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 context is implied via the parent_id behavior ('Omitted parent_id requests the whole tree, while an explicitly empty parent_id requests top-level comments only'), which helps an agent decide how to scope a call. However there is no explicit when-to-use-this-vs-alternative guidance relative to the several sibling archive/comment tools.

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