Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify product

shopify_product_get
Read-onlyIdempotent

Retrieve one Shopify product by handle and store, returning variants, images, collections, SEO, and stock details when the storefront exposes them.

Instructions

Get one Shopify product with its variants, images, collections, SEO, and stock detail where the store exposes it. 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_product_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 product 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.8/5.0
Behavior3/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 by structured data. The description adds only one genuine behavioral note — "where the store exposes it" — warning that some fields may be absent, but says nothing about pagination, rate limits, or how country/language alter returned prices.

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?

Two short sentences, with the capability and its return payload front-loaded before the prerequisite. Nothing is redundant or padded; every clause carries information.

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 single-resource getter with full schema coverage and rich annotations, the description covers purpose and return shape well enough to call correctly, and there is no output schema to require return-value explanation. Minor gap: it does not clarify how the country/language parameters affect the returned pricing and language data, which matters given seven parameters.

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 seven parameters including context, country, language, llm_model, and conversation_id are already fully documented in the schema. The description merely restates that handle and store are required, adding no syntax, format, or defaulting meaning beyond what the schema provides; the baseline 3 applies.

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?

States a specific verb and resource ("Get one Shopify product") and enumerates the payload it returns: variants, images, collections, SEO, and stock detail. The word "one" plus the field enumeration separates it from list/batch siblings like shopify_products_list and shopify_products_batch_get, and from narrower siblings like shopify_product_metafields_get and shopify_product_reviews_summary_get.

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?

The prerequisite is explicit ("Requires `handle` and `store`"), which implies the tool is for fetching a single known product. However, it never states when to prefer this over shopify_products_batch_get for multiple handles or shopify_product_availability_list for stock checks, so the routing decision is left to inference.

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