Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_posts_ids

Look up archived Reddit posts by comma-separated IDs to retrieve historical scores, comment counts, and removal categories, with missing IDs listed separately.

Instructions

Look up archived Reddit posts by ids. Looks up known Reddit post 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 and comment counts are snapshots, and removed_by_category is included when available.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are present, so the description carries full burden and largely meets it: it discloses the upstream request cap (two requests of up to 500 ids), duplicate removal, input-order preservation, separate listing of missing ids, and that scores/comment counts are snapshot values with removed_by_category only sometimes present. Auth, rate limits, and full response shape remain unstated.

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 four sentences are dense with actionable facts and front-load the purpose before the mechanics. The first and second sentences restate the same idea ('by ids' / 'known post ids'), a small redundancy that keeps it just shy of 5.

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?

For a one-parameter lookup with no output schema and no annotations, the description covers batching, ordering, dedupe, misses, and data-staleness well. Only the returned record shape and any prefix/t3_ handling nuance (left to the schema) are unaddressed, which is acceptable here.

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 single parameter is fully documented in the schema, so baseline is 4; the description still adds real meaning beyond it by specifying dedupe behavior, input-order result ordering, and separate handling of missing ids — semantics an agent cannot infer from the schema alone.

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?

States a specific verb and resource ('Look up archived Reddit posts by ids') and pins down the data source (Arctic Shift historical archive), which cleanly separates it from a search-style sibling like reddit_archive_posts_search that would be used to discover ids.

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?

Phrasing like 'look up known Reddit post ids' implies you must already have ids in hand, so discovering ids is implicitly out of scope. However, no sibling tool is named and no explicit when-not condition is given, so the routing guidance stays implicit.

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