Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify product metafields

shopify_product_metafields_get
Read-onlyIdempotent

Fetch merchant-exposed metafields for a single Shopify product using its store domain and handle, with optional namespace.key filters to target needed fields.

Instructions

Get merchant-exposed metafields for one Shopify product. 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_metafields_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysNoMetafield keys as `namespace.key`, comma-separated, up to 25. Defaults are `reviews.rating`, `reviews.rating_count`, `shopify.color-pattern`, `global.title_tag`, `global.description_tag` and `custom.color`.
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.
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, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact, that only merchant-exposed metafields are returned, but says nothing about rate limits, truncation of large metafields, or what happens when a key is absent.

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 purpose, with no filler. The second sentence largely repeats the schema's required fields, so it earns slightly less than full marks.

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?

For a simple read tool with four required parameters, full schema coverage and a complete annotation set, the definition is adequate to invoke correctly. However, with no output schema, an agent gets no sense from the description of what the returned metafield payload looks like or how missing keys are represented.

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 handle, store, keys, context, llm_model and conversation_id are all documented in the schema with patterns and defaults. The description only restates that handle and store are required, adding no meaning beyond the structured data, which is the baseline for full coverage.

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 metafields') scoped to 'one Shopify product', and the qualifier 'merchant-exposed' narrows what kind of metafields come back. It is distinguishable from shopify_product_get, but it never names a sibling to sharpen the boundary explicitly.

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 when-to-use or when-not-to-use guidance: nothing says whether to reach for this instead of shopify_product_get, or that it is limited to a single product handle. Usage is only implied by 'for one Shopify product'.

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