Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

hm_search

Search H&M product listings by free-text keyword to get pricing, images, colors, per-size stock, and search-quality metadata like spelling suggestions and related searches.

Instructions

Search H&M product listings by free-text keyword. Runs a free-text keyword search on H&M and returns products with pricing, images, colors, and per-size stock, plus search-quality metadata (a spelling-correction suggestion, related searches, and a content-filter flag). Unlike category browsing, an obscure or nonsense keyword returns a genuine empty result (zero products) rather than a fallback set. Pagination is page-based and real: requesting a page beyond the real last page returns a normal response with an empty products array rather than an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "hm_search"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number, one-based, defaults to 1
`query`	Yes	Free-text search keyword
`page_size`	No	Results per page, 1 to 72, defaults to 36

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.14.0Aug 21, 2026

TDQS

A4.1/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 behavioral burden and does so well: it discloses the returned fields (pricing, images, colors, per-size stock), the search-quality metadata, and two important edge cases – nonsense keywords yield a genuine empty result rather than a fallback, and out-of-range pages return an empty array rather than an error. It omits auth/rate-limit context, 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?

Four sentences, all substantive and front-loaded with purpose before edge cases. The opening two sentences restate the same idea ('search product listings by free-text keyword' / 'runs a free-text keyword search'), a minor redundancy.

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, so the description appropriately explains the return payload and pagination semantics itself. It is complete enough for an agent to call the tool correctly, with only the read-only safety profile left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so query, page, and page_size are already documented in the schema. The description adds only marginal parameter-relevant value via the pagination edge-case note, so the baseline 3 is appropriate.

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 (search) and resource (H&M product listings) and scopes it to free-text keyword input. It explicitly distinguishes itself from category browsing (hm_categories), so an agent can tell the two apart 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?

Gives clear context for when this applies (free-text keyword search) and contrasts it with category browsing as the alternative path. It does not, however, name the more obvious sibling alternatives such as hm_search_suggestions (autocomplete) or hm_product (direct lookup), so routing guidance is good but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server