Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bigcommerce_product

Fetch structured product details from a public BigCommerce Stencil storefront page by providing its full URL, returning clean JSON for commerce data workflows.

Instructions

Get a BigCommerce storefront product. Returns product detail from a public BigCommerce storefront product page. url must be the full public product-page URL for a BigCommerce Stencil storefront.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull public BigCommerce product page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It discloses that this reads a public storefront page and that the URL must belong to a BigCommerce Stencil storefront, which is genuinely useful scoping context. It says nothing about failure modes, rate limits, or what happens with non-Stencil URLs.

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 tight sentences that front-load the core action before the return behavior and the URL constraint. No padding, though the second sentence is somewhat redundant with the first.

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?

A single-parameter read tool with no output schema; the description covers what it fetches, what it returns at a high level, and the input constraint. Adequate for the complexity, though slightly more on expected response shape would help.

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 baseline is 3, but the description adds real meaning beyond the schema by constraining the URL to a full public product-page URL on a Stencil storefront, which the schema's shorter text does not convey.

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 and resource ("Get a BigCommerce storefront product") and clarifies it returns product detail from a public storefront page. It distinguishes itself from the similarly-named bigcommerce_search and bigcommerce_category by being single-product detail oriented, though it does not explicitly name those alternatives.

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?

Implies usage by requiring a full public product-page URL, which tells the agent when this tool applies versus a search/category tool. However, it never explicitly states when to prefer it over bigcommerce_search or bigcommerce_category, leaving routing to inference.

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