Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify store policies

shopify_store_policies_get
Read-onlyIdempotent

Retrieve a Shopify store's privacy, refund, shipping, terms, subscription, contact, or legal policy text by domain to answer customer questions or verify store terms.

Instructions

Get a Shopify store's privacy, refund, shipping, terms, subscription, contact and legal policies with their full text. Requires 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": {
      "store": "<store>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_store_policies_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.
policyNoOne policy kind, or omit for all of them: `privacy`, `refund`, `shipping`, `terms_of_service`, `terms_of_sale`, `subscription`, `contact` or `legal_notice`.
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

A3.6/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 that full policy text is returned, which hints at a verbose payload, but says nothing about missing-policy behavior, response size, or the context/llm_model/conversation_id protocol requirements that the schema carries.

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 zero waste; the resource and the full-text behavior are front-loaded and the requirement note closes it out.

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?

With five parameters, a fully documented schema, and complete annotations, the description needs only to frame what the tool returns and roughly what it covers, which it does. It falls short only on edge-case behavior (store without the requested policy) and on making the all-policies default explicit.

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 description echoes the enum values (privacy, refund, shipping, terms, subscription, contact, legal) but adds no meaning beyond the schema, and it blurs `terms_of_service` versus `terms_of_sale` into a bare 'terms'.

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 (Get) and resource (a Shopify store's policies) and enumerates the policy families covered, plus the notable detail that full text is returned. It is clear against siblings such as shopify_store_menu_get or shopify_store_redirects_list, though it never names a sibling to differentiate itself explicitly.

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: fetch policies when store policy text is needed. There is no statement of when to prefer this over related store tools, no note that omitting `policy` returns all kinds, and no guidance on handling stores that lack a policy. 'Requires `store`' just restates the schema.

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