Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bestbuy_product_reviews

Retrieves page one of a Best Buy product's customer reviews by SKU, returning normalized ratings, titles, text, authors, dates, and tags for quick analysis.

Instructions

Get a Best Buy product's customer reviews. Returns page 1 (up to 20) of one Best Buy product's normalized customer reviews (rating, title, text, author, posted date, tags such as Verified Purchaser, recommended flag, helpful/unhelpful counts), sourced from the product's dedicated reviews page. sku is the numeric Best Buy SKU shown on bestbuy.com product pages and URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skuYesNumeric Best Buy SKU

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.1/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, so the explicit statement that only page 1 with up to 20 reviews is returned is valuable. It also discloses the source (dedicated reviews page) and the fields provided, giving an agent a clear picture of the tool's behavior and limits.

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?

The description is compact and front-loaded with the main action and resource, followed by useful return data details. The list of fields is informative rather than redundant, and nothing appears to be filler.

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?

Given there is no output schema, the description sufficiently describes the return fields, source, and page limit. It is complete for a simple one-parameter read tool, though it stops short of explicitly covering ordering, filters, or alternative sibling tools.

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?

The schema already describes sku as 'Numeric Best Buy SKU' (100% coverage), and the description adds helpful context on how to discover it on bestbuy.com pages and URLs. This goes beyond the schema and helps an agent know where to locate the 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?

The description states a precise verb (Get), a specific resource (Best Buy product's customer reviews), and details what the returned data contains. This makes the tool's purpose immediately clear and distinguishes it from at least related sibling tools like bestbuy_product, bestbuy_product_questions, and bestbuy_product_related.

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 clearly implies when to use it: when a caller needs customer reviews for a specific Best Buy product. However, it does not explicitly contrast with alternatives or state when not to use it, such as when product questions or related products are the actual goal.

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