Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify collection

shopify_collection_get
Read-onlyIdempotent

Retrieve a single Shopify collection by handle and store, including its filter facets and counts for product filtering.

Instructions

Get one Shopify collection with its filter facets and counts. Requires handle and store.

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": {
      "handle": "<handle>",
      "store": "<store>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_collection_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
handleYesRequired. The collection handle, as it appears in its URL.
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

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), so the bar is lower. The description usefully discloses the payload content (filter facets and counts), but is silent on what happens for an unknown or private handle, and no output schema exists to fill that gap.

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?

Two short sentences, front-loaded with what is returned. The second sentence largely duplicates the schema's required list, which is mild waste, but there is no padding or tangents.

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 simple single-item read with fully documented parameters and annotations covering safety, the description gives enough to select and invoke the tool. Return-shape details beyond "facets and counts" are the only meaningful omission, and no output schema is present to compensate.

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 seven parameters including the required handle/store and the conversation_id and llm_model conventions. The description only restates that handle and store are required, adding no format or usage detail beyond the schema.

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 one Shopify collection") and adds scope detail that distinguishes it from a list operation by saying it returns filter facets and counts. It does not name the sibling list tool, but the singular resource makes the distinction inferable.

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?

Usage is only implied: "Get one ... collection" suggests a single-item lookup rather than a listing or search, and the note that it needs a handle and store tells the agent when it can be called. There is no explicit when-to-use/when-not or named alternative such as the collections list tool.

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