Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

homedepot_category

Browse a Home Depot category or brand page to get product titles, prices, images, ratings, total result count, and refinement facets for drill-down.

Instructions

Browse a Home Depot category or brand page. Returns one page of a Home Depot category or brand browse page's product grid: products with title, image, model, current/original price, and rating/review count, plus the category's total result count and the refinement facets the page offers. path is the segment of a /b/ URL after "/b/", e.g. "Tools-Power-Tools-Drills-Impact-Drivers/N-5yc1vZc29x"; a full https://www.homedepot.com/b/... URL or a "/b/..." path is also accepted. sort selects the result ordering and is one of best_match, top_sellers, top_rated, price_low_to_high, price_high_to_low, most_popular, delivery_date; omit it to keep the site's default ordering. page is a 1-indexed page number (default 1, maximum 42), 24 products per page. Each returned facet's path is directly usable as this endpoint's own path parameter to drill down. An unrecognized or blocked path returns an upstream error rather than an empty result.

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number, default 1, maximum 42 (12 products per page)
pathYesHome Depot category/brand browse path, e.g. \
sortNoResult ordering. One of: best_match, top_sellers, top_rated, price_low_to_high, price_high_to_low, most_popular, delivery_date. Omit for the site's default ordering

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.5
    • changedInput schema / properties / page / description
      Previous value: -"1-indexed page number, default 1, maximum 42 (24 products per page)"New value: +"1-indexed page number, default 1, maximum 42 (12 products per page)"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "best_match",
+  "top_sellers",
+  "top_rated",
+  "price_low_to_high",
+  "price_high_to_low",
+  "most_popular",
+  "delivery_date"
+]
  2. Changed2 schema fields changedv1.16.2
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-indexed page number, default 1, maximum 42 (24 products per page)",
+  "type": "integer"
+}
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Result ordering. One of: best_match, top_sellers, top_rated, price_low_to_high, price_high_to_low, most_popular, delivery_date. Omit for the site's default ordering",
+  "type": "string"
+}
  3. Addedv1.16.0

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 burden and does well: it enumerates the returned fields, notes the total result count and refinement facets, gives a hard pagination cap (42) and the drill-down mechanic, and warns that an unrecognized/blocked path returns an upstream error rather than an empty result. It omits auth/rate-limit context, but the behavioral disclosure is genuinely rich.

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 purpose and return contents before parameter detail, and every sentence carries information. It is slightly long and repeats the full sort enum already in the schema, which is the main 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?

For a 3-param read tool with no annotations and no output schema, the description supplies return shape, pagination limits, facet drill-down and error semantics. The main defect is an internal inconsistency: it states '24 products per page' while the schema says 12, which could mislead an agent reasoning about pagination.

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 nominally 100%, which sets a baseline of 3, but the description adds real value: it defines the path format (segment after '/b/', with an example and acceptance of full URLs), the 1-indexed default and max for page, and the default-ordering behavior for sort. This meaningfully compensates for the path schema description, which appears truncated in the input schema.

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 Home Depot category or brand page') and immediately describes what it returns, distinguishing it from homedepot_search (query-driven) and homedepot_product (single item). An agent can tell what this endpoint does 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 Guidelines3/5

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

The description implies the usage context (you need a /b/ category or brand path) and explains that facet paths can be reused as the path parameter to drill down. However, it never states when to prefer this over homedepot_search or how to obtain a path in the first place, leaving routing decisions to inference.

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