Skip to main content
Glama

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

adidas_search

Read-only

Search Adidas.com product listings by keyword, or browse a category listing by taxonomy slug (exactly one of query or category is required), with real pagination and sort options (price-low-to-high, newest-to-oldest, top-sellers, price-high-to-low): normalized product summaries (title, price, rating, images, color variants) plus facet filter groups, sort options, and a breadcrumb trail for category browse. An obscure keyword may return Adidas's own fallback results, and requesting a page beyond the available pages or an unknown category returns a not-found error.

Input 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.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Category/taxonomy slug, the path segment after /us/ in an Adidas category URL. Exactly one of query or category is required."
    • addedInput schema / properties / page / description
      Added value: +"One-based page number, defaults to 1"
    • addedInput schema / properties / query / description
      Added value: +"Search keyword. Exactly one of query or category is required."
    • addedInput schema / properties / sort / description
      Added value: +"Sort order. Allowed values: price-low-to-high, newest-to-oldest, top-sellers, price-high-to-low. Omitted means relevance."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, openWorld), and the description adds genuinely new behavioral context: fallback results for obscure keywords, and not-found errors for out-of-range pages or unknown categories. These edge-case behaviors are not derivable from annotations or schema.

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?

Front-loads the two search modes and the key constraint, then the return shape, then edge-case errors. Dense but every clause carries information; the colon-delimited return-field list is slightly packed but 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?

Covers the two invocation modes, the exclusivity rule, return content, pagination/sort behavior, and two failure modes. With an output schema present, return-value explanation is bonus rather than requirement, so nothing an agent needs is missing.

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

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value beyond the schema by restating the exactly-one-of constraint, describing category as the path segment after /us/, and enumerating the sort values inline — clarifying intent beyond raw field definitions.

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) plus resource (Adidas.com product listings) and enumerates two supported modes: keyword search and category-slug browse. This clearly distinguishes it from siblings like adidas_product (detail lookup), adidas_suggest (autocomplete), and adidas_stores.

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?

Explicitly states the mutual-exclusion rule (exactly one of query or category is required), which tells the agent how to invoke it. It stops short of naming alternative sibling tools for adjacent needs (e.g. adidas_suggest for query completion), so it is strong but not a full when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP toolsInspect
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