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 one page of product listings with prices, ratings, and refinement facets, plus total result count. Accepts a category path, sort order, and page number to return normalized product data.

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 (24 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.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"
+}
  2. Addedv1.16.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full burden, and it does so thoroughly: accepted path forms, sort values and default, page default/maximum, 24 products per page, facet drill-down behavior, and the upstream-error-on-blocked-path behavior are all disclosed. This goes well beyond a generic read/browse description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and output shape, then systematically details each parameter and edge behavior. Every sentence earns its place, and there is no filler or redundancy.

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

Completeness5/5

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

Given there is no output schema, the description appropriately explains the return contents (products with key fields, total count, facets) and covers pagination, sorting, path formats, and error behavior. An agent has enough information to invoke the tool correctly and interpret its results.

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

Parameters5/5

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

Although schema coverage is 100%, the description adds substantial meaning: it explains the exact path format with concrete examples, enumerates all sort values that are not schema enums, and clarifies page indexing and limits. The facet-path reuse note further enriches parameter semantics.

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 states a specific verb and resource: 'Browse a Home Depot category or brand page' and precisely describes the returned payload (normalized products, prices, ratings, total result count, facets). This clearly distinguishes it from siblings like homedepot_search and homedepot_product.

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 scopes the tool's intended input domain (a /b/ category or brand browse URL/path) and explains what it returns per page. It does not explicitly name alternative tools or state when not to use it, but the category/brand browse context is unambiguous enough for an agent to select it correctly.

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