Skip to main content
Glama
Sign In
shopify-multi-mcp

shopify-multi-mcp

by fledgeling-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Search products

search_products
Read-only

Search or list products in one Shopify store by query, tag, vendor, SKU, status, or inventory, returning IDs, titles, handles, totals, and price ranges.

Instructions

Search or list products in one store. Returns id, title, handle, status, vendor, type, tags, total inventory and price range. "query" uses Shopify search syntax, for example status:active vendor:Nike, tag:sale, title:hood*, sku:ABC-123, inventory_total:<5. Shopify ignores unknown filter fields and returns everything, so use documented fields only. Product ids are only valid in the store they came from.

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>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoPass pageInfo.endCursor from the previous result to get the next page.
firstNoHow many results to return (1-100).
queryNoShopify product search query. Omit to list recent products.
storeYesNo stores are connected yet. Call connect_store first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the return shape, explains that Shopify silently ignores unknown filter fields and returns everything, and warns that product IDs are store-scoped. These are meaningful behavioral details for correct invocation.

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 front-loaded with purpose and return fields, then moves into query syntax and critical caveats. Every sentence adds actionable information without repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although there is no output schema, the description lists the returned fields, explains query syntax, warns about ignored filters, and notes store-scoped IDs. Combined with full schema coverage and read-only annotations, it gives the agent enough context to call the tool correctly.

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?

With 100% schema coverage the baseline is 3, but the description adds valuable meaning for the 'query' parameter via Shopify syntax examples and the warning about unknown fields. It also reinforces the store-scoped nature of results, though after/first semantics remain schema-only.

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 states a specific verb/resource combination ('Search or list products') and scopes it to 'one store,' clearly separating it from all-store or non-product siblings. It also enumerates the returned fields, so an agent can tell exactly what this tool provides.

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?

It gives clear usage context for searching versus listing and explains that 'query' uses Shopify search syntax with concrete examples. It does not explicitly compare against siblings such as graphql_query or connect_store, so it is clear but not fully prescriptive about alternatives.

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