Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

reddit_archive_time_series

Query historical Reddit archive time-series metrics by absolute time range and precision; requests that could exceed 1,000 points are rejected.

Instructions

Get historical Reddit archive time series. Returns Arctic Shift's native time-series values. Supply an absolute creation-time range and a precision; ranges that could exceed 1,000 points are rejected. Counts, score sums, and retrieval-delay sums are archive metrics, not current Reddit totals. Arctic Shift says time-series data may be approximate and take hours or days to update.

Input Schema

NameRequiredDescriptionDefault
metricYesArchive metric
precisionYesTime bucket precision
subredditNoOptional subreddit scope; required for subreddit_subscribers, and unsupported for retrieval-delay metrics
created_afterYesAbsolute start time: epoch seconds/milliseconds or ISO 8601
created_beforeYesAbsolute end time: epoch seconds/milliseconds or ISO 8601

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?

With no annotations, the description carries the load and does so well: it discloses the 1,000-point rejection rule, that values are Arctic Shift's native (not Reddit's live) figures, and that data may be approximate and lag hours to days. Missing is a note on result shape/pagination, but the important behavioral traits are covered.

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?

Four short sentences, purpose front-loaded, then operational constraints, then the metric-definition warning, then the freshness caveat. Zero filler and no repetition of schema content.

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 five-parameter read tool with no annotations and no output schema, the description covers purpose, input constraints, metric semantics, and data staleness — everything needed to call it correctly and interpret results. Remaining detail (enums, subreddit rules) lives in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the enum values and formats are already documented. The description adds real meaning around the creation-time range being absolute and the precision driving the point limit, but says nothing about the subreddit parameter's conditional rules that the schema covers.

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 ("Get historical Reddit archive time series") and identifies the data source (Arctic Shift), which distinguishes it from the many Reddit post/comment sibling tools. It stops short of naming a sibling or contrasting the time-series view with per-post retrieval tools.

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 concrete operational guidance: supply an absolute creation-time range plus a precision, and stay under the 1,000-point ceiling or the call is rejected. It also warns that archive metrics are not current Reddit totals, which steers metric interpretation. It never explicitly names an alternative sibling for related needs.

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