Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

burberry_search

Search Burberry's product catalog by keyword to get normalized product summaries, facet filters with live counts, sorting options, and paginated results.

Instructions

Search Burberry products. Searches Burberry's product catalog by keyword. Returns normalized 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

TableJSON 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
Behavior5/5

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

With no annotations, the description carries full behavioral disclosure. It explains return content (normalized summaries, facets with live counts), pagination behavior (offset increments of 20), sort semantics, facet application syntax, empty-result handling, and the lack of a grand-total count. This is comprehensive and goes beyond what a schema would convey.

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 longer than minimal but each sentence contributes essential information. It front-loads the core purpose, then details facets, pagination, and edge cases. No redundant filler; structure is logical and efficient.

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?

Given no output schema, the description adequately describes return structure (normalized summaries, facets with counts) and important behavioral aspects like empty results and missing grand-total count. It lacks details on other potential response fields, but for a search tool it covers the essential information needed to call and interpret results.

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 baseline is 3. The description adds meaningful context for all parameters: it clarifies offset pagination increments, explains sort selection, and provides a concrete example for facets syntax. This exceeds baseline by detailing how parameters interact and what values mean.

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 a specific action ('Search Burberry products') and resource ('product catalog by keyword'). It also differentiates from a key sibling (burberry-category) by noting the absence of a grand-total count, making its purpose unambiguous.

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?

The description implies when to use this tool (for keyword-based search with facets and pagination) and explicitly contrasts with burberry-category, but does not explicitly state 'use this when' or list alternative tools. The context is clear enough for an agent to infer usage.

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