Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

bigcommerce_search

Search a public BigCommerce storefront by query and return one product-search page; provide the storefront origin, search text, and optional 1-indexed page.

Instructions

Search a BigCommerce storefront. Returns one product-search page from a public BigCommerce storefront. url must be the public storefront origin; an optional caller path or query is ignored. q is required search text. page is 1-indexed and defaults to 1.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>",
      "q": "<q>"
    },
    "name": "bigcommerce_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search text
`url`	Yes	Public BigCommerce storefront origin
`page`	No	1-indexed search page, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A3.7/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 burden and does reasonably well: it discloses the return granularity (one page), that results are scoped to public storefronts, and that any caller path/query is ignored — a genuinely useful behavior an agent would otherwise get wrong. It stops short of noting whether authentication is needed or how large a page is.

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?

Four short sentences, no filler, with the core behavior ('one product-search page') and the ignored-path caveat front-loaded. Efficient, though the url/query sentences could be tightened.

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 3-parameter, no-annotation, no-output-schema tool, the description covers the essentials an agent needs to call it correctly: valid url form, required q, pagination semantics, and the ignore-path behavior. Missing only return-shape detail, which is a minor gap given no output schema is defined.

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 q, url, and page are already documented per-parameter. The description largely restates the schema (q required, page 1-indexed defaulting to 1, url is the public origin) without adding syntax, format, or edge-case detail beyond it. Baseline 3 is appropriate.

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+resource ('Search a BigCommerce storefront') and clarifies the scope ('one product-search page from a public BigCommerce storefront'). It distinguishes itself from bigcommerce_product and bigcommerce_category by the storefront-wide search framing, though it never explicitly names those siblings.

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?

It gives concrete preconditions (url must be a public storefront origin, q is required search text) and a notable caveat (a caller-supplied path or query is ignored), which implicitly tells the agent this is a query-based search rather than a URL fetch. It does not, however, state when to prefer this over bigcommerce_product or bigcommerce_category.

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

Deploy Server