Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hm_search_suggestions

Fetch H&M search-box suggestions for a query, including spelling-complete phrases and merchandised results; omit the query to get trending and popular searches.

Instructions

Get H&M search-box suggestions. Returns H&M's own search-box typeahead suggestions. When query is given, returns spelling-complete phrase suggestions and merchandised content results. When query is omitted or empty, instead returns trending searches and popular-search shortcuts (phrase/content suggestions are both empty in that mode). search_history is not session-scoped -- it returns the identical list for every request, so treat it as fixed default content rather than a real per-caller history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search-box input; omit or leave empty for trending/popular searches instead

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it delivers real behavioral value: the dual-mode behavior, the fact that phrase/content suggestions are empty in trending mode, and especially the warning that search_history is not session-scoped and returns an identical list every request. That last point is exactly the kind of non-obvious behavior an agent needs, though auth/rate-limit/return-shape details are absent.

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 and appropriately sized, but the first two sentences are largely redundant ('Get H&M search-box suggestions' / 'Returns H&M's own search-box typeahead suggestions'), and the sentence about search_history references a field not present in the schema without introduction.

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?

For a single-parameter typeahead tool with no annotations and no output schema, the description covers both operating modes and the key non-obvious quirk, which is most of what an agent needs. Return-value detail is described at a high level (phrases, content results, trending, shortcuts) rather than fully specified.

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?

The single parameter already has 100% schema coverage (including the omit-for-trending behavior), so the baseline is 3. The description earns above baseline by explaining what each mode of the query parameter actually returns, which the schema does not.

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+resource ('Get H&M search-box suggestions') and immediately scopes it as typeahead/autocomplete rather than full search, which cleanly separates it from siblings like hm_search, hm_categories, and hm_product. An agent can identify the tool's role without opening the 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?

The description clearly branches usage on the query parameter: with a query you get phrase/content suggestions, without one you get trending/popular searches. That is effective when-to-use guidance, but it never names an alternative tool (e.g., hm_search) or states when this typeahead should be preferred over a real search.

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