Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store locations

shopify_store_locations_list
Read-onlyIdempotent

Lists physical locations for a Shopify store, returning addresses, coordinates, and phone numbers, with cursor pagination for larger result sets.

Instructions

List a Shopify store's physical locations with address, coordinates and phone. Requires store. Returns a list (use cursor when paginated).

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_locations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoLocations per page, 1 to 250. Default: 50.
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.
cursorNoCursor from `page.nextCursor` of the previous response. It only works with the same filters.
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.8/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, non-destructive, open-world operation, so the description needn't restate safety. It usefully adds that the result is a list containing address, coordinates, and phone, plus pagination guidance via cursor. It does not discuss rate limits, permissions, or response structure in more detail.

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?

The description is two short sentences, front-loads the core action and returned content, and has no filler. Every phrase contributes useful information for invoking the tool.

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 list tool with strong annotations and complete schema descriptions, this is largely complete. The lack of an output schema means the description could say more about the exact response shape, but it already identifies the key returned fields and cursor pagination.

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 fully documents parameters such as `store`, `limit`, `cursor`, `context`, `llm_model`, and `conversation_id`. The description only reinforces the `store` requirement and cursor behavior, adding little meaning 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?

The description states a specific verb and resource: list a Shopify store's physical locations. It also names the returned fields (address, coordinates, phone), which distinguishes it from sibling tools like shopify_store_get and various store content list tools, though it does not explicitly name those alternatives.

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 by the tool's purpose. The description notes that `store` is required and that a cursor should be used when paginated, but it gives no explicit when-to-use guidance, exclusions, or comparison to alternative location-related tools such as instagram_locations_search_list_v2 or facebook_marketplace_locations_search.

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