Skip to main content
Glama

commercebridge

by io.github.IsaiahDupree

Search Best Buy's product catalog

search_bestbuy
Read-onlyIdempotent

Search Best Buy's US product catalog by keyword and/or category, built on Best Buy's official Products API. Returns sku, title, sale/regular price, rating, manufacturer/model, image, online/in-store availability, and UPC per product. Errors honestly until this engine is fully live upstream: currently returns not_found (route not yet redeployed on the production commerce-api), then credentials_required once deployed without BESTBUY_API_KEY provisioned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeyword query. Required unless `category` is given. Matches across name, manufacturer, and description.
pageNoDefault 1.
limitNoDefault 20. Best Buy caps page size at 100.
categoryNoBest Buy categoryPath.id to constrain the search.

TDQS

A4.3/5.0
Behavior5/5

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

Beyond annotations, the description discloses non-obvious behavior: dependence on Best Buy's official Products API, the specific return fields, and two operational error states ('not_found' and 'credentials_required') with context on when they occur. This adds significant transparency.

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 sentences cover purpose, return data, and error behavior. Each sentence earns its place, though the last sentence about deployment status is slightly verbose. Overall well-structured and front-loaded with purpose.

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 no output schema, the description compensates by listing return fields. It also covers error scenarios and API source. It doesn't mention rate limits or pagination behavior, but these are partially addressed in the schema. Overall complete for a search tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds no substantive parameter details beyond what the schema already provides (e.g., 'keyword and/or category' mirrors the 'q' and 'category' descriptions).

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 clearly states the tool's function with a specific verb and resource: 'Search Best Buy's US product catalog by keyword and/or category.' It also distinguishes itself from siblings like get_bestbuy_product and other retailer-specific search tools, providing clear scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys when to use the tool (for searching by keyword and/or category) and implies 'get_bestbuy_product' is for direct product retrieval. However, it doesn't explicitly name alternatives or provide 'when not to use' scenarios, so it misses the top criterion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All commercebridge toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools are clearly distinguished by platform and entity (e.g., get_etsy_shop vs get_etsy_listing), but search_shopify and search_shopify_products have overlapping purposes and near-identical names, which could cause misselection. The individual descriptions help, but the boundary is fuzzy.

Naming Consistency4/5

The dominant pattern is get_<platform>_<entity> and search_<platform>_<entity>, which is clear and consistent. However, deviations like search_shopify_products (which lists all products rather than performing a filtered search) and the use of plural get_ebay_items for bulk retrieval break the clean verb_noun convention in a few places.

Tool Count5/5

14 tools across four distinct platforms is well-scoped, with each platform getting a focused set of search and get operations. This is comfortably within the ideal range and each tool serves a concrete purpose.

Completeness4/5

The server provides solid read-only coverage for product search and detail retrieval across four platforms. Minor gaps exist, such as no way to fetch products within a Shopify collection or list Best Buy categories, but these are workaround-able and do not severely impair agent workflows.

Resources