Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bestbuy_search

Search Best Buy's product catalog by keyword to retrieve product listings with SKU, title, URL, image, price, rating, and review count; supports pagination.

Instructions

Search Best Buy's product catalog. Returns one page (up to 24) of one Best Buy keyword search's product listing (sku, title, url, image, price, rating, review count). q is free-text search keywords, e.g. "laptop". page is the optional 1-indexed page number (defaults to 1); requesting a page past the last one returns an empty products list, not an error.

Input Schema

NameRequiredDescriptionDefault
qYesSearch keywords
pageNo1-indexed page number, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.3/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 the page cap (up to 24 results), the exact result fields (sku, title, url, image, price, rating, review count), and the important edge case that an out-of-range page returns an empty list rather than an error. Auth and rate-limit behavior are not mentioned, keeping it 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.

Conciseness5/5

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

Front-loaded with purpose, then return semantics, then parameter detail. Every sentence earns its place and there is no filler.

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?

No output schema exists, so the description must (and does) explain the return fields, page size, and pagination edge case. Nothing an agent needs to invoke and interpret the call correctly is missing.

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 the schema documents both params, but the description still adds value: it clarifies q is free-text keywords with a concrete example ('laptop') and explains the past-last-page behavior of page, which the schema does not.

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 (Search) and resource (Best Buy's product catalog), and is easily distinguished from sibling tools like bestbuy_product (detail), bestbuy_categories, and bestbuy_brands. The return shape is named up front, so an agent knows this is a keyword product search.

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 usage (search the catalog by free-text keywords) but names no alternatives and gives no explicit when-to-use vs when-not guidance relative to bestbuy_product or bestbuy_categories. Usage is inferable 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