Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_posts_search

Search archived Reddit posts by query, author, subreddit, or URL and narrow results with creation-date bounds.

Instructions

Search archived Reddit posts. Searches Arctic Shift's public historical post archive. Supply at least one of query, author, subreddit, or url; date bounds can further narrow that search. This is separate from the live Reddit search endpoint. created_after/created_before are time boundaries, not Reddit listing cursors; posts include created_utc and retrieved_on so callers can see when the archive captured each record. Archived scores and comment counts can lag changes for roughly 36 hours. A valid query with no matches returns an empty posts array. Slow or throttled upstream searches return 503 with Retry-After.

Input Schema

NameRequiredDescriptionDefault
urlNoLinked URL prefix filter
sortNoSort by creation time
limitNoMaximum posts, defaults to 25 and clamps to 100
queryNoText search across archived post titles and selftext
authorNoPublic Reddit username filter
subredditNoSubreddit name filter
url_exactNoRequire an exact URL match; requires url
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.6/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: it discloses the data source, that archived scores and comment counts can lag by roughly 36 hours, that posts include created_utc and retrieved_on, that no matches yield an empty posts array, and that throttled upstream searches return 503 with Retry-After. These details go well beyond what the schema alone conveys.

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?

The description is front-loaded with its purpose and then layers only relevant operational details: filter requirement, date semantics, archive latency, empty results, and 503 handling. Each sentence earns its place, and there is no filler or repetition.

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 nine-parameter historical search tool with a fully described schema and no output schema, the description covers the critical invocation context. It explains the archive source, required filter behavior, date boundary semantics, result and error cases, and timestamp fields. It does not describe pagination behavior or the full result shape, which leaves a small gap given the absence of an output schema.

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, but the description adds important semantics: at least one of query, author, subreddit, or url must be supplied despite none being formally required, and created_after/created_before are time boundaries rather than Reddit listing cursors. It does not add meaning for every parameter such as sort, limit, or url_exact, but the added constraints are materially useful.

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 opens with a specific verb and resource: 'Search archived Reddit posts.' It identifies the backend archive ('Arctic Shift's public historical post archive') and explicitly distinguishes this tool from the live Reddit search endpoint. An agent can immediately tell this is a historical search tool rather than a live or ID-lookup tool.

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 gives a concrete usage condition: 'Supply at least one of query, author, subreddit, or url,' and explains that date bounds narrow that search. It also states this is separate from the live Reddit search endpoint, which implicitly routes live/current queries elsewhere. It stops short of naming a specific sibling tool such as reddit_search or reddit_archive_posts_ids, so the alternative routing is clear but not fully explicit.

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