Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bestbuy_product

Retrieve a Best Buy product's details by numeric SKU, including name, brand, price, availability, rating, and images. Use it to fetch structured product data for a specific item.

Instructions

Get a Best Buy product's detail. Returns one Best Buy product's detail (name, brand, model, color, price, availability, rating, images, breadcrumbs). sku is the numeric Best Buy SKU shown on bestbuy.com product pages and URLs.

Input Schema

NameRequiredDescriptionDefault
skuYesNumeric Best Buy SKU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the returned fields (name, brand, model, color, price, availability, rating, images, breadcrumbs) and where the SKU comes from, which is genuinely useful, but says nothing about auth requirements, rate limits, or whether it is a pure read. Adds some value, not rich behavioral context.

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?

Three short sentences, front-loaded with the action, but the first two restate the same thing ('Get a Best Buy product's detail' and 'Returns one Best Buy product's detail'). Mild redundancy rather than bloat.

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 single-parameter lookup with no output schema and no annotations, the description compensates by enumerating the returned fields and defining the input format. Nothing critical is missing, though safety/auth context is absent.

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% and the schema already says 'Numeric Best Buy SKU'. The description goes beyond that by explaining the SKU is the numeric identifier shown on bestbuy.com product pages and URLs, i.e. how to source the value — meaningfully more than the schema provides.

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 (Get) and resource (a Best Buy product's detail) and clarifies it returns exactly one product, which implicitly separates it from list/search siblings like bestbuy_search. It does not, however, name the sibling a searching agent should use instead, so it stops short of a 5.

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?

Usage is only implied: an agent must already possess a SKU to call this. There is no explicit when-to-use vs bestbuy_search or bestbuy_product_related, and no guidance on prerequisites. Adequate minimum viability, but gaps are clear.

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