Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

stockx_search

Search StockX's product catalog by category, keyword, and filters like brand, color, gender, and availability; get matching product summaries with prices and total counts.

Instructions

Search/browse StockX products. Browses StockX's product catalog by category with optional free-text keyword search and facet filters (gender, brand, color, shoe height, activity, availability), returning product summaries with headline pricing plus the total matching count.

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed result page, defaults to 1
sortNoResult sort order, defaults to featured
brandNoFilter by one or more brand slugs, comma-separated, e.g. jordan,nike
colorNoFilter by color, comma-separated for multiple values
limitNoResults per page, defaults to 20, maximum 100
modelNoFilter by a single model slug, e.g. air-force-1. Requires exactly one value in brand
queryNoFree-text keyword search within the category, e.g. a model name or colorway
genderNoFilter by gender, comma-separated for multiple values
activityNoFilter by activity, comma-separated for multiple values
categoryYesStockX top-level category
shoe_heightNoFilter by shoe height, comma-separated for multiple values
xpress_shipNoOnly include products with StockX Xpress Ship availability
below_retailNoOnly include products currently trading below original retail price
available_nowNoOnly include products with at least one active ask

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.17.5
    • addedInput schema / properties / activity / enum
      Added value: +[
+  "basketball",
+  "football",
+  "golf",
+  "hiking",
+  "running",
+  "skateboarding",
+  "soccer"
+]
    • addedInput schema / properties / category / enum
      Added value: +[
+  "sneakers",
+  "shoes",
+  "apparel",
+  "accessories",
+  "collectibles",
+  "trading-cards",
+  "electronics"
+]
    • addedInput schema / properties / color / enum
      Added value: +[
+  "white",
+  "black",
+  "multi",
+  "blue",
+  "grey",
+  "pink",
+  "red",
+  "brown",
+  "yellow",
+  "green",
+  "purple",
+  "orange"
+]
    • addedInput schema / properties / gender / enum
      Added value: +[
+  "men",
+  "women",
+  "kids",
+  "unisex"
+]
    • addedInput schema / properties / shoe_height / enum
      Added value: +[
+  "low",
+  "mid",
+  "high"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "featured",
+  "most-active"
+]
  2. Added

TDQS

B3.4/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 does disclose useful output behavior ('returning product summaries with headline pricing plus the total matching count'), which helps the agent understand scope and pagination, but says nothing about read-only nature, rate limits, or authentication.

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?

Two sentences, no filler. Purpose is front-loaded and the capability/return detail follows immediately; every clause carries 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 14-parameter tool with no output schema and no annotations, the description compensates reasonably by summarizing what comes back (product summaries with pricing plus total count). It is slightly thin on pagination/sort semantics and the distinction from sibling product/category tools.

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 enums and defaults. The description only enumerates facet groups (gender, brand, color, shoe height, activity, availability) that the schema already specifies, adding no syntax or constraint detail beyond it.

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 ('Search/browse StockX products') and scopes it precisely: catalog browsing by required category with optional keyword and facet filters. It does not differentiate itself from close siblings such as stockx_product, stockx_categories, or stockx_brands, so an agent must infer the boundary.

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?

The description explains how the tool works (category browse + optional keyword + facets) but never says when to choose it over stockx_product, stockx_categories, or stockx_brands. There is no explicit when-to-use or when-not-to-use guidance, only implied browsing context.

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