Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stockx_product

Retrieve StockX product data from a URL slug, covering pricing, listings, market averages, and related items for resale research.

Instructions

Get StockX product detail. Returns a StockX product: identity (title, brand, model, colorway, style id, retail price, release date, description, image), current market data (lowest ask, highest bid, last sale, trailing average price/sales count, delivery-speed ask tiers), individual seller listings (price, condition, size), related-product recommendations (other colorways/siblings StockX surfaces on the product page), and any promotional badges.

Input Schema

NameRequiredDescriptionDefault
slugYesStockX product URL slug (the urlKey), the path segment of a https://stockx.com/{slug} product page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose a rich return shape (market data, seller listings, related colorways, promo badges). However, it says nothing about permissions, rate limits, caching, or whether missing/sold-out products error out. Decent read-side disclosure, significant operational gaps.

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 purpose is front-loaded in the first clause, followed by a single structured sentence enumerating return categories. It is long but each item earns its place because no output schema exists to carry that information.

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 tool with no output schema and no annotations, the description compensates well by itemizing what comes back, which is the main thing an agent needs to decide whether to call it. The missing piece is usage context: how to obtain a slug and when a sibling tool is preferable.

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%; the schema itself already explains that slug is the urlKey path segment of stockx.com/{slug}. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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?

'Get StockX product detail' is a specific verb+resource that an agent can immediately place relative to stockx_search, stockx_brands and stockx_releases. It also enumerates the payload categories (identity, market data, listings, related products, badges), so the scope of the resource is unambiguous. It stops short of explicitly naming the sibling used to find a product, so it isn't a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool versus alternatives such as stockx_search (to find a slug) or stockx_releases. Usage is only implied by the required slug parameter. Nothing tells the agent what to do if it lacks a slug.

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