Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store pages

shopify_pages_list
Read-onlyIdempotent

List a Shopify store's pages with body HTML, summaries, SEO details, and timestamps to audit content or research competitor stores. Use cursor pagination for large page sets.

Instructions

List a Shopify store's pages with body HTML, summary, SEO and timestamps. 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_pages_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows 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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the return payload shape and the pagination mechanic, but says nothing about rate limits, empty results, or whether fetch cost scales with page count — modest added value beyond structured data.

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 and return contents, with no filler. Slightly terse in that the cursor hint is parenthetical rather than explained.

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?

No output schema exists, so enumerating returned fields (body HTML, summary, SEO, timestamps) is genuinely necessary and present, and the pagination note covers the main operational risk. Required bookkeeping params (context, llm_model, conversation_id) are fully specified in the schema, so the description need not repeat them.

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 every parameter including `store`, `cursor` and `limit` is fully documented in the schema; baseline 3 applies. The description only restates the `store` requirement and reinforces cursor usage, adding no syntax or format detail the schema lacks.

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 ('List a Shopify store's pages') and enumerates what comes back (body HTML, summary, SEO, timestamps), which is enough to separate it from shopify_articles_list or shopify_blogs_list. It stops short of naming a sibling or scope 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a conditional hint ('use cursor when paginated') and notes the `store` requirement, implying the tool is for enumerating a store's pages. It offers no when-to-use versus alternatives (e.g., sitemap listing or a single-page get) and no exclusions.

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