Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify blog articles

shopify_articles_list
Read-onlyIdempotent

Lists articles from a Shopify blog with full content and author details, supporting cursor-based pagination via store domain and blog handle.

Instructions

List the articles in one Shopify blog with full content, author and paging. Requires blogHandle and 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": {
      "blogHandle": "<blogHandle>",
      "store": "<store>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_articles_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoArticles per page, 1 to 250. Default: 10.
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.
blogHandleYesRequired. The blog handle, as it appears in its URL, e.g. `news`.
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
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds value beyond them by disclosing that results include 'full content, author and paging' — a material payload-size signal — and that paging requires a cursor; it omits rate limits and the public-storefront restriction, which the schema does cover.

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 sentences, front-loaded with purpose, then requirements, then return shape — nothing redundant. It is close to ideal for a small list tool; only the parenthetical paging note feels slightly compressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter, 4-required tool with no output schema, the description covers purpose and prerequisites but leaves the multi-step conversation_id/cursor protocol entirely to the schema. Since the schema is fully documented, it is adequate but thin — an agent would need the schema to call this safely.

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 baseline is 3. The description restates that blogHandle and store are required and points at the cursor for pagination, but adds no syntax or format detail beyond the schema, and it omits any mention of the analytics/context parameters (context, llm_model, conversation_id) that are also required.

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 the articles in one Shopify blog') and scopes it to a single blog, which separates it from store-wide listings like shopify_blogs_list. It is clear but never names the sibling it complements (shopify_article_get for single-article retrieval), so sibling differentiation is implied rather than explicit.

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?

Prerequisites are stated ('Requires blogHandle and store') and a paging hint is given ('use cursor when paginated'), which is genuine when-to-use context. However, it never says when to prefer shopify_article_get, or that blogHandle must first come from shopify_blogs_list, so the guidance stops at implied usage.

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