Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store collections

shopify_collections_list
Read-onlyIdempotent

List a Shopify store's collections with descriptions, images, and SEO data to inspect or audit a public storefront. Use the store domain and paginate with a cursor when results are split.

Instructions

List a Shopify store's collections with descriptions, images and SEO. Requires store. 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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_collections_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows per page, 1 to 250. Default: 50.
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.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered. The description adds modest value by saying what is returned (descriptions, images, SEO) and that results are paginated with a cursor, but says nothing about ordering, completeness of the collection set, or failure modes such as invalid/unreachable storefronts.

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 the core action and return contents. Minor waste in 'Requires `store`', which the schema already marks as required, but nothing else is padding.

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 read-only paginated list tool with no output schema and fully described parameters, the description covers what it returns and how pagination continues, which is most of what an agent needs. It could still be richer about whether all collections (including unpublished) are returned, but it is adequate for the tool's complexity.

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 all six parameters including store, limit and cursor are already documented in the schema; the baseline of 3 applies. The description only restates the `store` requirement and the cursor's purpose, which duplicates schema text rather than adding 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 ('List a Shopify store's collections') and enumerates the returned facets (descriptions, images, SEO), which lets an agent separate it from sibling list tools like shopify_collection_products_list or shopify_products_list. It does not explicitly name or contrast a sibling, so it falls short of a 5.

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?

The only usage direction is 'use cursor when paginated', which is pagination mechanics rather than when-to-use guidance. There is no statement of when to pick this over shopify_collection_products_list or shopify_store_get, and no prerequisites or exclusions beyond the bare 'Requires `store`'.

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