Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store reviews

shopify_store_reviews_list
Read-onlyIdempotent

Fetch a Shopify store's published store-wide reviews, ratings, and review media; sort, filter by rating, and paginate with a cursor.

Instructions

List a Shopify store's store-wide reviews, ratings and review media the store publishes. 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_reviews_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNo`newest` (default), `rating`, `helpful` or `with_photos`. A sort the store's reviews do not support is ignored.
limitNoReviews per page, 1 to 250. Default: 25.
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.
ratingNoOnly reviews with this star rating, 1 to 5.
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, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds only that results are a list and that pagination uses a cursor; it says nothing about ordering behavior, whether unsupported filters silently degrade, or how much data exists.

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 the resource and scope front-loaded, the required input next, and the return/pagination note last. Nothing is padded and nothing important is buried.

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 listing tool with full schema coverage, annotations and no output schema, the definition covers what the agent needs to invoke it. The only real gap is sibling disambiguation against the product-level reviews tool, which is a guidance rather than completeness issue.

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 the sort enum, limit bounds and cursor reuse constraint is already documented. The description adds only that `store` is mandatory, which the schema's required list already encodes; baseline 3 is appropriate.

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 store-wide reviews, ratings and review media. The qualifier 'store-wide' implicitly separates it from the sibling shopify_product_reviews_list, but that sibling is never named, so the agent must infer the boundary.

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?

Says the `store` parameter is required and that a cursor should be used when paginating, which is actionable context. It gives no explicit when-to-use/when-not guidance and does not route the agent to the product-level or summary alternatives.

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