Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

burberry_search

Search Burberry’s product catalog by keyword to retrieve product summaries and live facet filters with per-option counts, then paginate or sort results.

Instructions

Search Burberry products. Searches Burberry's product catalog by keyword. Returns product summaries plus the upstream's own available filters (facets) with live per-option result counts. offset paginates in increments of 20 (the upstream's own fixed page size). sort selects the result order. facets applies a facet selection back, a comma-separated list of property:value pairs taken from this same response's facets field (e.g. benefit:bags,dotcomreportingcolour:black). A query with no matches, or a facet combination with no matches, returns a well-formed empty result, not an error. Unlike burberry-category, this response has no true grand-total result count -- only the current page's own count.

Input Schema

NameRequiredDescriptionDefault
sortNoSort order
queryYesSearch keyword
facetsNoComma-separated property:value facet filters, taken from this same response's own facets field, e.g. benefit:bags,dotcomreportingcolour:black -- at most one value per property
offsetNoZero-based result offset, in increments of 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 that offset uses the upstream's fixed page size of 20, that empty results (query or facet combination) are well-formed rather than errors, and that no true grand-total count is returned. It does not mention rate limits or auth, but for a public catalog search this is above-average disclosure.

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?

Purpose is front-loaded, followed by the pagination, sort, facet, empty-result, and sibling-comparison facts. Every sentence conveys a distinct operational detail with no filler.

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?

With no output schema and no annotations, the description still tells the agent what comes back (product summaries plus the response's own facets with live counts), how to paginate, how to feed facets back, and how empty results behave. Nothing essential for a correct call 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, but the description adds real semantics: offset must move in increments of 20 (the upstream page size), facets is a comma-separated property:value list with a worked example and a one-value-per-property constraint, and sort controls result order. This meaningfully exceeds the terse schema descriptions.

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 and resource ('Search Burberry products... by keyword') and explicitly contrasts with the sibling burberry_category on a concrete dimension (absence of a true grand-total count). An agent can distinguish the two without opening either schema.

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?

Explains how to use facets (values must be drawn from this same response's facets field) and how to paginate (offset in increments of 20), plus differentiates from burberry-category. It stops short of stating explicit when-to-use/when-not rules versus the category tool, so it is clear context rather than full routing guidance.

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