Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify store

shopify_store_get
Read-onlyIdempotent

Fetch a Shopify store's identity, brand, market, payment settings, policy summary, and agent-commerce capabilities by domain to evaluate storefront details and commerce readiness.

Instructions

Get a Shopify store's identity, brand, market, payment settings, policy summary and agent-commerce capabilities. 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_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.
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.
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's main added value is disclosing what the call returns (payment settings, policy summary, agent-commerce capabilities), which matters because there is no output schema; however it says nothing about storefront reachability failures, auth needs, or rate limits.

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?

A single front-loaded sentence names the resource and its returned facets efficiently. The trailing 'Requires `store`' is redundant with the schema's required list and in-parameter 'Required.' text, a small waste but not disruptive.

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, open-world getter with no output schema, enumerating the returned facets is the key compensating information, and it is present. Usage routing against the narrower store sub-resources is the main omission, but the agent has enough to invoke the tool correctly.

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 explains `store` host normalization, `context`, `country` defaults, `llm_model` and the `conversation_id` echo/sequencing rule in detail. The description only repeats that `store` is required and adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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?

Uses a specific verb and resource ('Get a Shopify store') and enumerates the returned facets (identity, brand, market, payment settings, policy summary, agent-commerce capabilities), which lets an agent distinguish it from narrower siblings like shopify_store_policies_get or shopify_store_menu_get. It stops short of explicitly naming those siblings as scoped-down alternatives, so differentiation is implied by the field list rather than stated.

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; the only directive is 'Requires `store`', which merely restates the required parameter. An agent has to infer from the returned-field list that this is the top-level store overview and that policy-specific queries may belong to shopify_store_policies_get.

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