Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store sitemap

shopify_store_sitemap_list
Read-onlyIdempotent

Retrieve a Shopify store's sitemap index or a typed child sitemap, including last-modified dates and image metadata, to map product, collection, page, blog, or article URLs.

Instructions

Get a Shopify store's sitemap index or one typed child sitemap, with last-modified dates and image metadata. 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_sitemap_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoChild sitemap page, 1 to 10,000. Default: 1.
typeNoThe child sitemap to return: `product`, `collection`, `page`, `blog`, `article`, `metaobject_page` or `agentic_discovery`. Omit for the sitemap index.
limitNoEntries per page, 1 to 250. Default: 250.
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.
localeNoThe locale path prefix, e.g. `de-ch`. Omit for the root locale.
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.7/5.0
Behavior4/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 beyond that by disclosing what comes back (last-modified dates, image metadata) and how pagination works via cursor, which is behavior-relevant and not derivable from the annotations.

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?

Three short sentences are front-loaded with the core action and its return content, with no filler. The 'Requires `store`' line is slightly redundant given the required-field schema, which is the only real slack.

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 nine parameters and no output schema, the description does the needed compensating work by describing the returned fields and pagination model. It is slightly thin on how the index response differs from a typed child response, but nothing essential for a correct call is missing.

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%, including the `type` enum and the cursor's `page.nextCursor` origin, so the schema does the heavy lifting. The description only repeats the `store` requirement and hints at cursor pagination, adding little meaning beyond what the schema already documents.

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 uses a specific verb and resource pair ('Get a Shopify store's sitemap index or one typed child sitemap') and distinguishes the two modes of the tool itself. It does not explicitly differentiate from the similarly named sitemap siblings (medium_sitemap_index_get, medium_sitemap_entities_list), which keeps it short of a 5.

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 description states the prerequisite ('Requires store') and gives one operational rule ('use cursor when paginated'), which is genuinely useful context. However, it offers no guidance on when to pick a specific `type` versus omitting it, and no comparison or exclusion against the other sitemap-listing tools, so selection guidance is only implied.

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