Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

boots_search

Search Boots UK products and categories, apply price, stock, and facet filters, and sort results by relevance, price, rating, or seller.

Instructions

Search Boots UK products and categories. Returns one page of Boots UK's public product catalog, including product cards and live facets. Supply q, one or more hierarchical category keys, or both. Use repeatable filter=facet_key:option_key values from that response's dynamic facets, plus the dedicated price and stock controls. sort accepts relevance, price_low_to_high, price_high_to_low, top_rated, best_seller, or newest.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text product query; required unless category is supplied
pageNoPage from 1 through 1000
sortNoSort: relevance, price_low_to_high, price_high_to_low, top_rated, best_seller, or newest
filterNoRepeat a dynamic facet filter as facet_key:option_key, using key/option values returned in facets; category, currentPrice, and inStock use their dedicated parameters
categoryNoRepeat the exact category hierarchy keys from root through the desired leaf; required unless q is supplied
in_stockNotrue hides out-of-stock items; false leaves stock unfiltered
page_sizeNoResults per page from 1 through 48
price_maxNoInclusive maximum GBP price; may be combined with price_min
price_minNoInclusive minimum GBP price; may be combined with price_max

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • addedInput schema / properties / category / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / filter / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "price_low_to_high",
+  "price_high_to_low",
+  "top_rated",
+  "best_seller",
+  "newest"
+]
  2. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that only one page is returned, that results come from Boots UK's public catalog, and that facet filters derive from the response's dynamic facets. It could add caveats about empty results or rate limits, but for a search tool it is reasonably transparent.

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?

Two sentences deliver a large amount of actionable guidance with no filler. Key usage rules are front-loaded, and the sort enum is briefly restated in a compact form that complements the schema.

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?

For a search tool with 9 parameters, 100% schema coverage, and no output schema, the description covers the core query modes, filtering mechanism, dedicated controls, and sort options. It does not need to restate schema-provided details like page ranges, and the description gives enough context for an agent to call this tool correctly.

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 by explaining the q/category relationship, how repeatable dynamic facet filters work, and that price and stock have dedicated controls—information beyond the raw schema field 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?

The description clearly states a specific verb and resource: 'Search Boots UK products and categories.' It further specifies the return payload ('product catalog, including product cards and live facets'), which distinguishes it from related tools like boots_suggest. The scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives strong guidance on how to structure queries ('Supply q, one or more hierarchical category keys, or both') and how to use filters. However, it never explicitly contrasts this tool with alternatives such as boots_suggest, so an agent must infer when one is preferable over the other.

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