Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

hermes_category

Browse a Hermès category to fetch product pages with SKU, title, price, colour, size, stock, images, facets, and category details. Supply a category code from the discovery endpoint.

Instructions

Browse a Hermès category. Browses one Hermès product category and returns a page of products (SKU, title, price with currency, colour, size, stock, images) plus the facet groups Hermès offers for that category, and the category's own title and description. The category parameter takes a category code from hermes-categories, which is the discovery endpoint for every accepted value. Page size is fixed at 48 by Hermès and cannot be changed. Prices are returned with the ISO-4217 currency for the selected market, since Hermès itself publishes bare numbers.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based result page; page size is fixed at 48. Page 1 is fully validated; pages beyond 1 are best-effort and provisional
sortNoResult order. One of: relevance, priceasc, pricedsc. Non-default sorts are best-effort
localeNoMarket and language. One of: at_de, au_en, be_en, be_fr, br_pt, ca_en, ca_fr, ch_de, ch_fr, cz_en, de_de, dh_en, dk_en, es_es, fi_en, fr_fr, gr_en, hk_en, ie_en, it_it, jp_ja, kr_ko, lu_fr, mo_en, mx_es, my_en, nl_en, no_en, pl_en, pt_en, ri_en, se_en, sg_en, th_en, tw_zh, uk_en, us_en
categoryYesHermès category code, from hermes-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 it discloses real behavioral traits: page size is fixed at 48 by Hermès and cannot be changed, and prices come back with an ISO-4217 currency tied to the selected market because Hermès publishes bare numbers. It does not cover error behavior or rate/permission requirements, keeping it short of a 5.

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-loaded with the purpose and then the return shape and constraints. Slightly wasteful in that 'Browse a Hermès category.' and 'Browses one Hermès product category' restate the same idea, but the rest of the prose is dense and earns its place.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the facet groups, plus the immutable page size and currency semantics. Only the relationship to sibling browse/search tools is left implicit, so it is nearly but not fully complete.

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 meaning beyond the schema: the category code must be sourced from hermes-categories, the page size constraint tied to the 'page' parameter is fixed at 48, and currency is bound to the locale/market selection. That is useful interpretation the schema alone does not supply.

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 Hermès category') and then enumerates exactly what is returned: products with SKU, title, priced currency, colour, size, stock and images, plus facet groups and the category title/description. It also explicitly routes to the sibling discovery endpoint hermes-categories, so an agent can distinguish it from hermes_products/hermes_search without opening a 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?

Gives a clear prerequisite and alternative: the category code must come from hermes-categories, which is named as the discovery endpoint for every accepted value. That is strong routing guidance, but it does not say when to prefer this over hermes_products or hermes_search, nor any exclusions.

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