Crawlora MCP

stockx_product

Read-only

StockX product detail: identity, current market data (lowest ask, highest bid, last sale, trailing averages), individual seller listings, related-product recommendations, and promotional badges.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "stockx_product"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	StockX product URL slug (the urlKey), the path segment of a https://stockx.com/{slug} product page.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower. The description adds meaningful behavioral context by disclosing the breadth of the payload — live market data, individual listings, recommendations, promo badges — which tells the agent this is a rich composite fetch, not a minimal record.

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?

A single front-loaded sentence that identifies the resource first, then lists contents. The parenthetical grouping of market metrics is efficient. The content list is slightly long but each item earns its place by signaling available data.

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 read-only single-parameter tool with a full output schema and 100% schema coverage, the description does enough: it characterizes what comes back and carries no burden for return-shape details. Nothing essential to correct invocation is missing.

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 coverage is 100% and the single slug parameter is fully documented in the schema (URL slug/urlKey with example). The description adds no format or syntax detail beyond that. Baseline 3 is appropriate.

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?

The description names the resource (StockX product) and enumerates the specific payload: identity, market data (lowest ask, highest bid, last sale, trailing averages), seller listings, recommendations, and badges. This is clearly a detail-fetch tool, distinct from stockx_search/brands/categories. It stops short of explicitly naming the siblings it is not.

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?

Usage is implied rather than stated: an agent infers this is called with a slug once the product is identified, but the description never says when to use it versus stockx_search or stockx_releases, nor that a slug must first be obtained. No exclusions or prerequisites are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?