Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

homedepot_search

Search Home Depot product listings by keyword and page to get titles, images, prices, ratings, review counts, and total results.

Instructions

Home Depot keyword search. Returns one page of a Home Depot keyword search's product listing: products with title, image, model, current/original price, and rating/review count, plus the search's total result count. A page carries up to 24 products, or up to 12 when Home Depot answers the query with a category page. q is free-text search keywords, e.g. "impact driver". page is a 1-indexed page number (default 1). An unrecognized/blocked query returns an upstream error rather than an empty result.

Input Schema

NameRequiredDescriptionDefault
qYesFree-text search keywords, e.g. \
pageNo1-indexed page number, default 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.9/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 discloses return fields, page size variability (24 normally, 12 on category pages), presence of a total result count, and that blocked/unrecognized queries surface an upstream error instead of an empty list. It omits any auth/rate-limit context, so it falls short of a 5.

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?

Purpose is front-loaded and every sentence carries information (return shape, page limits, error behavior). The enumeration of return fields is slightly listy but earns its place given there is no output schema.

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?

With no output schema and no annotations, the description compensates fully: it documents the return payload, page size behavior, and error semantics. An agent has everything needed to call it and interpret the response.

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 100% so baseline is 3, but the description adds value beyond the schema: it supplies a concrete example query ('impact driver') that the truncated schema description for q lacks, and restates that page is 1-indexed with default 1. Useful query-formulation guidance without extra syntax.

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 ('Home Depot keyword search') and immediately scopes the output to one page of a product listing. It is clearly distinguishable from siblings like homedepot_product or homedepot_category by function, though it never names an alternative tool explicitly.

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 makes the use case (find products by free-text keyword) inferable, but gives no explicit when-to-use/when-not guidance and does not route the agent to homedepot_category, homedepot_product, or homedepot_suggest for other needs. Usage is implied rather than stated.

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