Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bigcommerce_category

Browse a BigCommerce storefront category to retrieve one product-listing page from a public URL, with 1-indexed paging defaulting to page 1.

Instructions

Browse a BigCommerce storefront category. Returns one product-listing page from a public BigCommerce storefront category page. url must be the full public category-page URL. page is 1-indexed and defaults to 1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull public BigCommerce category page URL
pageNo1-indexed category page, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A3.5/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 burden. It usefully discloses that it returns one paginated product-listing page from a 'public' storefront (implying no auth), but does not describe sort order, page size, fields returned, or error behavior when a URL isn't a valid category page.

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 core action and result, then parameter notes. No padding or redundancy beyond the minor restatement of schema-documented parameter facts.

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 two-parameter, no-output-schema browse tool, the description covers what it does, what it returns (a page of products), and pagination. Return-field details aren't required given no output schema. Slightly incomplete on validation/edge behavior, but otherwise adequate.

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 schema already fully documents both parameters, and the description largely restates them ('full public category-page URL', '1-indexed, defaults to 1'). Baseline 3 applies since the schema does the heavy lifting.

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 clear verb+resource: 'Browse a BigCommerce storefront category' returning a product-listing page. This distinguishes it from siblings like bigcommerce_product and bigcommerce_search (which target a single product or query results). It does not explicitly name those alternatives, 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 implied: use this when you have a category-page URL and want its product listing. There is no explicit guidance on when to pick this over bigcommerce_search or bigcommerce_product, nor any stated prerequisites beyond the URL requirement.

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