Skip to main content
Glama
Sign In

commercebridge

by io.github.IsaiahDupree
OverviewDiscussionsAdmin

Keyword-filter a Shopify store's catalog

search_shopify
Read-onlyIdempotent

Filter a public Shopify store's catalog by keyword across title, vendor, product type, and tags — keyless, live now.

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": {
      "store": "<store>",
      "q": "<q>"
    },
    "name": "search_shopify"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeyword filter, e.g. "wool runner". Required.
limitNoDefault 50.
storeYesShopify store domain, e.g. allbirds.com. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds valuable context beyond annotations: it specifies that the store must be public, requires no key, operates on live data, and searches specific fields. This meaningfully clarifies behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly written sentence with no filler. It front-loads the core action and includes only high-signal additions ('keyless, live now') that are not redundantly stated in the annotations.

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 the tool's simplicity, strong annotations, and fully documented schema, the description covers the key operational context: public access, keyless usage, live data, and search scope. It does not describe return format, but no output schema exists and the absence is acceptable for a straightforward search tool.

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%, providing descriptions for all three parameters. The description adds extra meaning by listing which fields the keyword applies to ('title, vendor, product type, and tags'), enriching the semantics of the 'q' parameter beyond the schema's basic example.

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?

The description states a specific verb ('Filter') and resource ('public Shopify store's catalog') with clear scope ('by keyword across title, vendor, product type, and tags'). It is unambiguous, though it does not explicitly distinguish itself from the sibling tool 'search_shopify_products'.

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 implies usage for public Shopify stores with no API key ('keyless, live now'), but it does not state when to use this tool instead of alternatives like 'search_shopify_products', nor does it mention any exclusions or conditions.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources