Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Shopify store

shopify_search_list
Read-onlyIdempotent

Search a Shopify store's products, articles, and pages by store and query, with filters, facets, and result counts; returns a cursor-paginated list.

Instructions

Search a Shopify store's products, articles and pages, with the store's facets and result count. Requires store and query. Returns a list (use cursor when paginated).

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>",
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRestrict the search to `product`, `article` or `page`. Default: all three.
limitNoRows per page, 1 to 250. Default: 50.
queryYesRequired. What to search for in the store.
storeYesRequired. The store's domain, for example `allbirds.com`, `www.allbirds.com` or `weareallbirds.myshopify.com`. A full URL is accepted and reduced to its host. Only public storefront hosts are accepted.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
countryNoISO 3166-1 alpha-2 country used for prices, currency and language, e.g. `GB`. Default: the store's own market.
languageNoTwo-letter language code, e.g. `EN`. Default: the store's own language.
priceMaxNoHighest product price to include.
priceMinNoLowest product price to include.
availableNoOnly products with an available variant.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral details beyond that: it returns a list with facets and result count, and advises using the cursor when paginated. It could go further on rate limits or auth, but it adds real value over the annotations.

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?

The description is compact and front-loaded with the primary purpose. The sentence about required parameters is slightly redundant with the schema's required fields, but overall it is efficient and easy to scan, with no extraneous wording.

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 13-parameter search tool with full schema coverage and annotations covering safety, the description provides adequate context: purpose, required inputs, return shape, and pagination hint. It does not need to explain the many filter parameters because the schema does so thoroughly, though it could note that results span only public storefront hosts.

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 documents all 13 parameters including store, query, cursor, country, language, price filters and availability. The description only reiterates that store and query are required and mentions cursor for pagination, adding no parameter semantics beyond what the schema provides. A 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?

The description states a specific verb and resource: search a Shopify store's products, articles and pages. It clearly distinguishes the scope from single-resource list tools, but it does not name or differentiate from siblings like shopify_search_suggest_list or shopify_products_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites beyond required parameters. The search purpose implies usage, but the description offers no routing context for an agent choosing among the many sibling list/search tools.

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