Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

reddit_archive_comments_search

Search archived Reddit comments by text, author, subreddit, post, or parent comment, then narrow results with creation-date bounds to find historical discussions.

Instructions

Search archived Reddit comments. Searches Arctic Shift's public historical comment archive. Supply at least one of query, author, subreddit, link_id, or parent_id; date bounds can further narrow that search. query searches comment body text and must be combined with author, subreddit, link_id, or parent_id; it maps to Arctic Shift's body parameter. Arctic Shift may time out or throttle broad searches, which return 503 with Retry-After. created_after/created_before are time boundaries, not Reddit listing cursors. Each comment includes created_utc and retrieved_on; archived scores can lag changes for roughly 36 hours. A valid query with no matches returns an empty comments array.

Input Schema

NameRequiredDescriptionDefault
sortNoSort by creation time
limitNoMaximum comments, defaults to 25 and clamps to 100
queryNoFull-text search within comment bodies; requires author, subreddit, link_id, or parent_id
authorNoPublic Reddit username filter
link_idNoReddit post id to scope comments
parent_idNoParent comment id; an explicitly empty value selects top-level comments
subredditNoSubreddit name filter
created_afterNoCreation-time lower bound; accepts epoch seconds or milliseconds, ISO 8601 dates, or relative offsets such as 1year, 2d, or 5min
created_beforeNoCreation-time upper bound; accepts epoch seconds or milliseconds, ISO 8601 dates, or relative offsets such as 1year, 2d, or 5min

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 warns that broad searches may be throttled and return 503 with Retry-After, explains that date bounds are time boundaries rather than listing cursors, discloses a ~36h staleness lag on archived scores, and states that a no-match query returns an empty comments array instead of erroring.

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?

Front-loaded with the purpose and dense with distinct operational facts; each sentence carries information. Minor waste from restating the archive identity ('archived Reddit comments' then 'Arctic Shift's public historical comment archive') and repeating the query-combination rule already present in the schema.

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 9-parameter search tool with no output schema and no annotations, the description covers input preconditions, throttling, freshness and the empty-result shape. It does not sketch the comment object beyond created_utc/retrieved_on, but the essential calling behavior is fully covered.

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 parameter descriptions already do the heavy lifting, but the prose adds non-obvious meaning: query maps to Arctic Shift's `body` parameter and must be paired with a scoping filter, and created_after/created_before are absolute time bounds, not Reddit cursors. That is real value beyond the schema text.

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 ('Search archived Reddit comments') and identifies the source as Arctic Shift's public historical archive, which distinguishes it from a live Reddit search. However, it never names the adjacent tools (reddit_comments, reddit_archive_comments_ids, reddit_archive_comments_tree) so the agent must infer the split from the word 'archived' alone.

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?

Gives a concrete precondition ('supply at least one of query, author, subreddit, link_id, or parent_id'), which matters because the schema lists none of them as required, and states the query-combination rule. It stops short of saying when to pick this over reddit_comments or the ids/tree variants, so exclusions are absent.

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