Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

hm_listing

Fetch a H&M category's product listing from H&M's app backend, returning normalized products with pricing, images, colors, and per-size stock. Use category slugs and page-based pagination.

Instructions

Browse an H&M category's product listing. Returns one H&M category's product listing page: normalized products with pricing, images, colors, and per-size stock, sourced from H&M's own app-backend listing data. category_id is an H&M category slug (e.g. ladies_newarrivals_all, men_newarrivals_all, ladies_jeans) -- this build does not expose a category/nav-tree discovery endpoint, so category_id values are currently sourced from known H&M storefront paths rather than a lookup call. Pagination is page-based and real: requesting a page beyond the category's real last page returns a normal response with an empty products array rather than an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, one-based, defaults to 1
sortNoSort order, defaults to RELEVANCE
is_newNoOptional filter for newly added items only
page_sizeNoResults per page, 1 to 72, defaults to 36
category_idYesH&M category slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "RELEVANCE",
+  "NEWEST_FIRST",
+  "PRICE_ASCENDING",
+  "PRICE_DESCENDING"
+]
  2. Addedv1.14.0

TDQS

A3.5/5.0
Behavior4/5

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

No annotations, so the description carries the burden. It discloses real behavioral detail: page-based pagination where out-of-range pages return an empty products array, and that data comes from H&M's app-backend listing data. Read-only nature is implied but not explicitly stated.

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 informative, front-loaded with purpose and response contents, then category_id and pagination quirks. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, response contents, pagination behavior, and category_id sourcing, but omits the clearly available hm_categories sibling as a source for category IDs and does not explicitly state read-only or system limits. Given the moderate complexity, it is close but has a notable gap.

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 already documents all 5 parameters (100% coverage), so baseline is 3. The description adds value by giving category_id slug examples and explaining that values are sourced from known storefront paths, plus clarifying page semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Browse an H&M category's product listing' and enumerates what the response contains (normalized products with pricing, images, colors, stock). It is distinguishable from hm_product (single product) and hm_search (search), though it doesn't explicitly name siblings; the claim that no category/nav-tree discovery endpoint exists is questionable given the hm_categories sibling.

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

Usage Guidelines2/5

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

No explicit when-to-use or alternative guidance. It describes the category_id sourcing limitation but doesn't point an agent to hm_categories (which appears in sibling tools) for finding category IDs, and doesn't state when not to use this tool.

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