Crawlora MCP

stockx_search

Read-only

Search StockX products by category, gender, brand, color, size, activity, and price, optionally with text; results include a matching count. Use stockx_brands and stockx_categories to discover filters or stockx_product for one item.

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": {
      "category": "<category>"
    },
    "name": "stockx_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-indexed result page. Defaults to 1.
`sort`	No	Result sort order. Allowed values: featured (default), most-active (top selling).
`brand`	No	Filter by one or more brand slugs, comma-separated, e.g. jordan,nike. StockX's brand catalog is large and changes over time -- see the endpoint documentation for commonly available values; any lowercase-hyphenated brand slug is accepted and passed through to StockX. See GET /stockx/brands for the current full catalog.
`color`	No	Filter by color. Allowed values: white, black, multi, blue, grey, pink, red, brown, yellow, green, purple, orange. Comma-separate multiple values.
`limit`	No	Results per page. Defaults to 20, maximum 100.
`model`	No	Filter by a single model slug (e.g. air-force-1), e.g. as found in a StockX brand page URL like stockx.com/brands/nike?model=air-force-1. StockX scopes this filter to one selected brand, so it requires exactly one value in brand; a comma-separated brand list is rejected when model is set. Model slugs are not enumerated by this API -- pass one captured from a StockX URL.
`query`	No	Optional free-text keyword search within the category, e.g. a model name or colorway.
`gender`	No	Filter by gender. Allowed values: men, women, kids, unisex. Comma-separate multiple values.
`activity`	No	Filter by activity. Allowed values: basketball, football, golf, hiking, running, skateboarding, soccer. Comma-separate multiple values.
`category`	Yes	StockX top-level category. Allowed values: sneakers, shoes, apparel, accessories, collectibles, trading-cards, electronics.
`shoe_height`	No	Filter by shoe height (sneakers/shoes categories). Allowed values: low, mid, high. Comma-separate multiple values.
`xpress_ship`	No	Only include products with StockX Xpress Ship availability.
`below_retail`	No	Only include products currently trading below original retail price.
`available_now`	No	Only include products with at least one active ask.

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

A4.1/5.0

Behavior3/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds that results include a matching count and that filters are passed through to StockX. It does not disclose pagination behavior, rate limits, or empty-result handling, so it adds modest value beyond annotations.

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 core action and filter axes, followed by sibling routing. Efficient, though the filter enumeration slightly overlaps with what the schema already provides.

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?

The tool has an output schema (so return values need not be explained) and comprehensive annotations. The description covers purpose, routing to siblings, and the matching count. It is complete enough for an agent to call correctly, though pagination/sort semantics could have been surfaced.

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 schema already documents all 14 parameters including enum values and the model/brand coupling constraint. The description repeats the filter list but adds no format or syntax detail beyond the schema. Baseline 3 is correct when the schema does the heavy lifting.

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 (Search) and resource (StockX products) and enumerates the filter axes (category, gender, brand, color, size, activity, price, text). This distinguishes it from siblings like stockx_product (single item) which the description explicitly names.

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

Usage Guidelines5/5

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

Explicitly routes to alternatives: 'Use stockx_brands and stockx_categories to discover filters or stockx_product for one item.' Names the conditions and the sibling tools, leaving nothing to inference.

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?