Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_comments_ids

Fetch archived Reddit comments by ID from Arctic Shift, returning ordered results and listing missing IDs separately.

Instructions

Look up archived Reddit comments by ids. Looks up known Reddit comment ids in Arctic Shift's historical archive. Supply 1 to 1,000 comma-separated ids; duplicates are removed, results follow input order, and missing ids are listed separately. The service sends at most two upstream requests of up to 500 ids each. Archived scores are snapshots, and removed_by_category is included when available.

Input Schema

NameRequiredDescriptionDefault
idsYesComma-separated Reddit comment ids (1-1,000); optional t1_ prefixes are accepted

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/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 behavioral burden and does so well: duplicates are removed, results follow input order, missing IDs are listed separately, and the service sends at most two upstream requests of up to 500 IDs each. It also discloses archive-specific behavior such as scores being snapshots and removed_by_category being included when available.

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 description is front-loaded with purpose and then adds operational constraints. It is mostly efficient, though the second sentence largely restates the first before adding the archive name, which is slight redundancy.

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?

No output schema exists, so the description must carry return-value context; it does explain missing-ID handling, snapshot scores, and removed_by_category. It does not fully describe the response structure, but for a focused ID-batch lookup it is substantially complete.

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?

The schema already fully documents the ids parameter, including the 1-1,000 range and optional t1_ prefixes. The description adds meaningful semantics about deduplication, result ordering, missing IDs, and upstream batching, though it does not add further ID-format detail beyond the schema.

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 states a specific verb and resource: "Look up archived Reddit comments by ids," and explicitly scopes it to "known Reddit comment ids in Arctic Shift's historical archive." The "by ids" phrasing and archive scope distinguish it from sibling tools like reddit_archive_comments_search and reddit_archive_comments_tree.

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?

It clearly establishes the usage context: callers should have known comment IDs and can supply 1 to 1,000 comma-separated IDs. It does not explicitly name when to use reddit_archive_comments_search or reddit_comments instead, so it lacks full alternative routing guidance.

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