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 retrieve normalized product listings, prices, ratings, and refinement facets for one result page.

Instructions

Browse a Home Depot category or brand page. Returns one page of a Home Depot category or brand browse page's product grid: normalized 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

TableJSON 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

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does describe return content and error behavior, but it contains a critical contradiction: the description states '24 products per page' while the input schema's `page` parameter says '12 products per page'. This inconsistency actively misleads the agent about pagination, undermining transparency.

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?

The description is somewhat long but well-structured)Skip? It starts with the primary purpose, then covers parameters, return details, and error behavior. Every sentence adds substantive information. A slight trim could improve it, but it remains effective and front-loaded.

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?

The description covers what is returned, path format, sort options, pagination, and error behavior. It is largely complete for a browse endpoint, but the incorrect products-per-page count creates a contradiction that leaves the agent unsure about actual pagination. This gap prevents a higher score.

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

Parameters2/5

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

Schema coverage is 100%, so a baseline of 3 applies. The description adds useful context for `path` (format and example) and `sort` (enum meanings), but it also directly contradicts the schema on the products-per-page value for `page`. This false information outweighs the added value, justifying a lower score.

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?

The description clearly states it browses a Home Depot category or brand page, describes the resource and the action. It differentiates from siblings like homedepot_search by focusing on category/brand browse pages. The phrase 'Browse a Home Depot category or brand page' is specific and unambiguous.

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 provides clear guidance on what the `path` parameter should be, including examples and accepted formats. It also explains sort options and page limits, and notes that facet paths are directly reusable for drilling down. However, it does not explicitly contrast with alternatives like homedepot_search or homedepot_categories, leaving the when-to-use decision partially implicit.

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