Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify search suggestions

shopify_search_suggest_list
Read-onlyIdempotent

Fetch a Shopify store's search suggestions across products, collections, pages, articles, and queries from a partial query; supply the store domain and query to receive a completion list.

Instructions

Get a Shopify store's search suggestions across products, collections, pages, articles and queries. Requires store and query. Returns a list.

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_suggest_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, 1 to 10. Default: 10.
queryYesRequired. The partial query to suggest completions for.
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.
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.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no note on rate limits, partial-query matching behavior, whether suggestions are ranked, or the per-call analytics/conversation plumbing that the tool actually demands.

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 purpose and listing the covered suggestion types. The trailing 'Returns a list' is near-filler given the schema, but the whole definition is tight with no wasted clauses.

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

Completeness3/5

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

An agent reading only the description would not learn that three of the four required parameters are meta/analytics plumbing (context, llm_model, conversation_id) rather than search inputs, which is a real surprise for a tool with 8 parameters. Since no output schema exists, the description's bare 'Returns a list' leaves the result shape mostly unstated, though the input schema is rich enough to carry the rest.

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 baseline is 3; the schema already explains store host normalization, limit range, and the country/language defaults. The description's 'Requires `store` and `query`' merely repeats the schema's required list and adds no new meaning.

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 and resource ('Get a Shopify store's search suggestions') and enumerates the suggestion surfaces (products, collections, pages, articles, queries), which clearly marks it as an autocomplete-style tool rather than a full search like the sibling shopify_search_list. It never names that sibling, so the differentiation is inferable but not explicit.

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 guidance on when to use this versus shopify_search_list or the other search_suggest siblings; the description only restates which parameters are required. 'Returns a list' describes output shape, not a selection criterion.

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