Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

burberry_category

Fetch one page of 20 products from a Burberry category listing. Supports sorting, offset pagination, and facet filters to refine results.

Instructions

Browse a Burberry category. Returns one page (20 products) of a Burberry category/browse listing. category is the site-relative category path, e.g. /l/womens-clothing/new-arrivals/ -- use burberry-categories to discover every valid value instead of guessing from site URLs. offset paginates in increments of 20 (the upstream's own fixed page size). sort selects the result order. The response includes the upstream's own available filters (facets) with live per-option result counts; feed a selection back in via facets, a comma-separated list of property:value pairs taken from this same response's facets field (e.g. benefit:bags,dotcomreportingcolour:black -- see a live response for the values valid for that category). At most one value per facet property; an unmatched or invalid combination returns a well-formed empty result, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order
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
categoryYesSite-relative category path -- see burberry-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A5/5.0
Behavior5/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 so well: it reveals the fixed 20-item page size, offset behavior, that responses include live facet counts, that at most one value per facet property is allowed, and that invalid/mismatched facet combinations produce a well-formed empty result rather than an error.

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?

The description is dense but every sentence earns its place, with the core behavior front-loaded and the most complex behavior (facets) explained in detail. There is no filler or restating of the tool name.

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?

Even without an output schema or annotations, the description tells the agent what it returns (20 products plus facets with counts), how to discover valid category paths, how to paginate, and how to handle invalid facet input. All information needed to invoke it correctly is present.

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 coverage is already 100%, but the description adds meaning: category must come from burberry-categories, offset is tied to the upstream's fixed 20-item page, sort selects result order, and facets are a comma-separated list of response-derived property:value pairs with a one-value-per-property constraint and a concrete example.

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: browse a Burberry category and return one page of 20 products. It also distinguishes itself from sibling tools by referencing burberry-categories as the way to discover valid category values.

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?

Tells the agent when to call this (category/browse listing), how pagination and sorting work, and explicitly routes category-value discovery to burberry-categories instead of guessing from site URLs. The facet guidance further instructs how to feed selections from a prior response back into the call.

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