Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bestbuy_product_reviews

Fetch up to 20 customer reviews for a Best Buy product using its numeric SKU, with ratings, text, author, date, and verified-purchase tags.

Instructions

Get a Best Buy product's customer reviews. Returns page 1 (up to 20) of one Best Buy product's customer reviews (rating, title, text, author, posted date, tags such as Verified Purchaser, recommended flag, helpful/unhelpful counts). 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.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the pagination behavior ('Returns page 1 (up to 20)'), which is genuine behavioral context, but says nothing about permissions, rate limits, sorting, or error handling for an invalid SKU.

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?

Two sentences, front-loaded with the core action, and the parenthetical field list is justified because no output schema exists. It is a touch dense but nothing is wasted.

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, low-complexity tool with no output schema and no annotations, the description supplies the missing return-field inventory and the pagination cap. It omits ordering and failure behavior, which are minor gaps for this tool class.

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 labels the parameter 'Numeric Best Buy SKU', so the baseline is 3. The description goes slightly beyond by telling the agent the SKU is 'shown on bestbuy.com product pages and URLs', which helps an agent source a valid value.

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 and resource: 'Get a Best Buy product's customer reviews.' The resource (customer reviews) cleanly separates it from siblings like bestbuy_product, bestbuy_product_questions, and bestbuy_search, so an agent can route to it without opening a schema.

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 the obvious use case (fetch reviews for a known SKU) but never states when to use this over alternatives, nor any prerequisites or exclusions. There is no routing guidance beyond the self-evident purpose.

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