Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stockx_releases

Retrieve StockX's upcoming release calendar by date, listing new and restocked products with summaries, headline pricing, and published release dates.

Instructions

Get StockX upcoming release calendar. Returns a date-ordered page (release date ascending) of StockX's upcoming release calendar: new and restocked products releasing on or after the given date, with product summaries, headline pricing, and each item's published release date.

Input Schema

NameRequiredDescriptionDefault
fromNoOnly include releases on or after this date (YYYY-MM-DD, UTC). Defaults to today
pageNo1-indexed result page, defaults to 1
limitNoResults per page, defaults to 20, maximum 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that results are date-ordered ascending and include product summaries, headline pricing and release dates, but says nothing about read-only nature, pagination limits, or how large the calendar can be. Adequate but incomplete for a no-annotation tool.

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?

Two sentences, front-loaded with the purpose before the return details. Slightly redundant in repeating 'upcoming release calendar' twice, but overall efficient and well-structured.

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?

With no output schema and no annotations, the description compensates by describing the returned fields (summaries, pricing, release dates) and ordering. It is nearly complete for an agent to call it correctly, though pagination behavior and read-only nature go unstated.

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 'from', 'page' and 'limit' are already fully documented (format, default, max). The description restates the date-filter semantics but adds no syntax or meaning beyond the schema, so baseline 3 applies.

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 ('Get') and resource ('StockX upcoming release calendar') and clarifies the scope as new and restocked products releasing on or after a date. This is clearly distinguishable from siblings like stockx_search, stockx_product, stockx_brands and stockx_categories.

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?

The description implies the use case (upcoming calendar) and the date-scoping behavior, but never states when to prefer this over stockx_search or stockx_product, nor any exclusions. Usage is inferrable but not guided.

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