Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goat_search

Find sneakers, streetwear, and collectibles on GOAT by free-text query or facet filters, returning product summaries with pricing, stock status, and total match count.

Instructions

Search GOAT products. Searches or browses GOAT's sneaker/streetwear/collectibles catalog by free-text query and/or facet filters (category, footwear sub-type, activity, color, gender, condition, brand, release year, price range, release-date range, silhouette, designer, in-stock/under-retail/instant-ship, curated collection), returning normalized product summaries (brand, silhouette, category, image, stock status, headline pricing across all sizes) plus the total matching count. Query is optional -- a facet filter alone browses the catalog the same way GOAT's own category/brand pages do. Credential-free public data from the same JSON API backing GOAT's own search page.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed result page, defaults to 1
sortNoResult sort order, defaults to relevance
limitNoResults per page, defaults to 12, maximum 100
queryNoFree-text search query, e.g. a model name, colorway, or style code. Optional -- omit to browse by facet filters alone
yearsNoFilter by season year(s), comma-separated, e.g. 2025,2026. See GET /goat/search/facets for the current live list
brandsNoFilter by one or more brand slugs, comma-separated, e.g. air-jordan,nike. GET /goat/search/facets lists GOAT's top brands; long-tail brands are valid here even when absent from that list
colorsNoFilter by color, comma-separated for multiple values
gendersNoFilter by gender, comma-separated for multiple values
in_stockNoOnly include products currently in stock
designersNoFilter by one or more designers, comma-separated, matching GOAT's own naming (see a product's designer field)
activitiesNoFilter by activity (sneakers only), comma-separated for multiple values
categoriesNoFilter by category, comma-separated for multiple values. See GET /goat/search/facets for the current live list
conditionsNoFilter by item condition, comma-separated for multiple values
silhouettesNoFilter by one or more silhouettes, comma-separated, matching GOAT's own naming (see a product's silhouette field)
instant_shipNoOnly include products with GOAT Instant Ship availability
under_retailNoOnly include products currently trading below original retail price
product_typesNoFilter by footwear sub-type, comma-separated for multiple values
released_afterNoOnly include products released on or after this date (YYYY-MM-DD, UTC)
collection_slugNoScope results to a GOAT curated collection (see GET /goat/collection), combinable with query, every other filter, and sort
price_cents_maxNoOnly include results priced at or below this amount, in cents
price_cents_minNoOnly include results priced at or above this amount, in cents
released_beforeNoOnly include products released on or before this date (YYYY-MM-DD, UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.17.5
    • addedInput schema / properties / activities / enum
      Added value: +[
+  "lifestyle",
+  "basketball",
+  "running",
+  "skateboarding"
+]
    • addedInput schema / properties / categories / enum
      Added value: +[
+  "footwear",
+  "apparel",
+  "accessories",
+  "bags",
+  "collectibles",
+  "media",
+  "sports",
+  "jewelry",
+  "home",
+  "objects",
+  "other",
+  "art"
+]
    • addedInput schema / properties / colors / enum
      Added value: +[
+  "black",
+  "white",
+  "blue",
+  "grey",
+  "red",
+  "green",
+  "pink",
+  "cream",
+  "brown",
+  "purple",
+  "multi-color",
+  "orange",
+  "tan",
+  "yellow",
+  "silver",
+  "gold",
+  "teal",
+  "copper"
+]
    • addedInput schema / properties / conditions / enum
      Added value: +[
+  "new_no_defects",
+  "used",
+  "new_with_defects",
+  "goat_clean"
+]
    • addedInput schema / properties / genders / enum
      Added value: +[
+  "men",
+  "youth",
+  "infant",
+  "women"
+]
    • addedInput schema / properties / product_types / enum
      Added value: +[
+  "sneakers",
+  "sandals",
+  "cleats",
+  "boots",
+  "slip-ons"
+]
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "newest",
+  "price_asc",
+  "price_desc",
+  "discount"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses credential-free/public access, the source API, and the return payload shape (summaries with brand, silhouette, image, stock status, headline pricing, total count). It does not discuss rate limits, pagination caps, or error behavior, which keeps it below a 5.

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?

Three dense sentences with no filler. The primary action is front-loaded, the optional-query behavior is explained in the second sentence, and the authentication/source note is in the third. Every sentence earns its place.

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 22-parameter tool with no output schema, the description is thorough: it explains scope, filter modalities, return payload, and credential requirements. It is slightly incomplete in not covering default sort behavior, result-page mechanics beyond the schema, or potential rate limits, but these are adequately handled by schema descriptions.

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 baseline is 3. The description's prose lists filter categories (category, color, brand, price range, etc.) but adds no syntax or format details beyond what each parameter's schema description already provides.

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'), a specific resource (GOAT's sneaker/streetwear/collectibles catalog), and the expected output (normalized product summaries plus total matching count). It also clarifies the query-optional browsing mode, which distinguishes this from product-detail, facet, collection, and suggestion siblings.

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

Usage Guidelines4/5

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

Provides clear context: free-text query and/or facet filters, with the explicit note that a facet filter alone browses the catalog like GOAT's category/brand pages. It does not name sibling alternatives or state when not to use this tool, so it stops short of a 5.

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