Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

adidas_search

Search Adidas products by keyword or browse category pages with pagination, sorting, and facet filters. Returns product summaries with prices, ratings, images, and color variants.

Instructions

Search or browse Adidas products. Searches Adidas.com product listings by keyword, or browses a category listing by taxonomy slug, with real pagination and sort options. Exactly one of query or category is required. Returns normalized product summaries (title, price, rating, images, color variants) plus facet filter groups, sort options, and (for category browse) a breadcrumb trail. Keyword search is best-effort relevance, not a guaranteed match: an obscure keyword returns whatever Adidas's own search index surfaces. A genuinely empty keyword search returns an empty product list, and requesting a page beyond the available result pages (or an unknown category) returns a not-found error. Category values are the path segment after /us/ in an Adidas category URL (e.g. women-athletic_sneakers); they can also be read from the url fields of a search/category response's own filters and breadcrumbs. Facets are applied by composing them into the category slug rather than by a separate parameter: each filters[].values[].slug is a token you splice into the category value (e.g. category=women-black-athletic_sneakers applies the Color=Black facet, and category=women-athletic_sneakers-prime applies Shipping=PRIME). Use filters[].key (the facet's stable name, e.g. searchcolor) rather than filters[].id, which is an opaque per-deployment UUID that cannot be used to build a request. Note the token's position within the slug varies by facet, so compose from a slug you have seen rather than assuming a fixed order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based page number, defaults to 1
sortNoSort order. Allowed values: price-low-to-high, newest-to-oldest, top-sellers, price-high-to-low. Omitted means relevance.
queryNoSearch keyword. Exactly one of query or category is required.
categoryNoCategory/taxonomy slug, the path segment after /us/ in an Adidas category URL. Exactly one of query or category is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description takes full responsibility and does an excellent job. It discloses that keyword search is best-effort relevance, that empty queries return empty lists, that out-of-range pages return not-found errors, and explains how facets compose into the category slug. This is far beyond minimal disclosure.

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?

The description is long but dense with necessary information. It is well-structured, starting with the tool's purpose, then clarifying the mutual exclusivity of query/category, then return format, then error behavior, then facet composition. Each sentence contributes meaningfully; only slight redundancy in explaining facets could be trimmed, but it's justified.

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?

Given the complexity of this tool (mutually exclusive params, facet slug composition, best-effort search behavior), the description is exceptionally complete. It covers return values, error cases, how to derive category slugs, and how to apply facets. No output schema is needed; the description suffices for an agent to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 the parameters. However, the description adds significant detail that the schema lacks: the exact meaning of category (path segment after /us/), the facet composition mechanics, and the distinction between query and category. It even explains how to derive category values from response fields.

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?

The description clearly states the tool does two things: search by keyword or browse by category, with a specific verb and resource. It distinguishes itself from related tools like adidas_product and adidas_suggest, and explicitly discusses differences within the description (e.g., keyword search vs category browse).

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?

The description explicitly states that exactly one of query or category is required, and provides guidance on when to use search vs browse. It also details how facets are applied via category slugs, and warns against using filters[].id. This is comprehensive and goes beyond basic 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