Crawlora MCP

goat_search

Read-only

Search or browse GOAT sneakers, streetwear, and collectibles with text and catalog facets such as category, size, color, brand, price, and stock. Use goat_suggest for typeahead, goat_curated for featured rails, or goat_collection for one editorial collection.

Input Schema

Name	Required	Description
`page`	No	1-indexed result page. Defaults to 1.
`sort`	No	Result sort order. Allowed values: relevance (default, best-match), newest (most recently released first), price_asc, price_desc.
`limit`	No	Results per page. Defaults to 12, maximum 100.
`query`	No	Free-text search query, e.g. a model name, colorway, or style code. Optional -- omit to browse by facet filters alone.
`years`	No	Filter by release year(s), comma-separated, e.g. 2025,2026.
`brands`	No	Filter by one or more brand slugs, comma-separated, e.g. air-jordan,nike. GOAT's brand catalog is large and changes over time, so this is not a fixed enum -- any lowercase-hyphenated brand slug is accepted and passed through.
`colors`	No	Filter by color. See GET /goat/search/facets for the current live list. Comma-separate multiple values.
`genders`	No	Filter by gender. See GET /goat/search/facets for the current live list. Comma-separate multiple values.
`in_stock`	No	Only include products currently in stock.
`designers`	No	Filter by one or more designers, comma-separated, matching GOAT's own naming exactly (e.g. Peter Moore). Not enumerable by this API -- take a value from GET /goat/product/{slug}'s designer field.
`activities`	No	Filter by activity (sneakers only). Allowed values: lifestyle, basketball, running, skateboarding. Comma-separate multiple values.
`categories`	No	Filter by category. See GET /goat/search/facets for the current live list. Comma-separate multiple values.
`conditions`	No	Filter by item condition. See GET /goat/search/facets for the current live list. Comma-separate multiple values.
`silhouettes`	No	Filter by one or more silhouettes, comma-separated, matching GOAT's own naming exactly (e.g. Air Jordan 1). Not enumerable by this API -- take a value from GET /goat/product/{slug}'s silhouette field.
`instant_ship`	No	Only include products with GOAT Instant Ship availability.
`under_retail`	No	Only include products currently trading below original retail price.
`product_types`	No	Filter by footwear sub-type. Allowed values: sneakers, sandals, cleats, boots, slip-ons. Comma-separate multiple values.
`released_after`	No	Only include products released on or after this date (YYYY-MM-DD, UTC). Finer-grained than the years filter, and combinable with it.
`collection_slug`	No	Scope results to one of GOAT's curated collections (see GET /goat/collection), combinable with query, every other filter, and sort. Collection slugs are not enumerable by this API -- capture one from a live GOAT page.
`price_cents_max`	No	Only include results priced at or below this amount, in cents.
`price_cents_min`	No	Only include results priced at or above this amount, in cents.
`released_before`	No	Only include products released on or before this date (YYYY-MM-DD, UTC). Finer-grained than the years filter, and combinable with it.

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 7, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds no behavioral context beyond the schema (no pagination, rate, or result-shape notes). Adequate but thin given annotations carry the burden.

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, zero waste, with the core capability front-loaded and the routing guidance following. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values need no description, and all 22 params are documented in the schema. Combined with the sibling routing, an agent has everything needed to call it correctly.

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?

With 22 parameters at 100% schema description coverage, the schema does the heavy lifting. The description mentions some facet categories (color, brand, price, stock) but adds nothing beyond the schema about syntax or defaults. Baseline 3 is correct.

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 specific verbs (search/browse) and the resource (GOAT sneakers, streetwear, collectibles), and enumerates the facet dimensions available. It also names the sibling tools it is not, so an agent can distinguish it from goat_suggest/goat_curated/goat_collection without opening schemas.

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 the agent: goat_suggest for typeahead, goat_curated for featured rails, goat_collection for one editorial collection. This is a clear when-to-use-alternative mapping.

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.