Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Shopify store blogs

shopify_blogs_list
Read-onlyIdempotent

List a Shopify store's blogs with their SEO details, authors, and recent articles, and page through results using the returned cursor.

Instructions

List a Shopify store's blogs with their SEO, authors and recent articles. 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_blogs_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoBlogs per page, 1 to 250. Default: 20.
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.7/5.0
Behavior4/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 real context beyond that: the returned payload includes SEO, authors and recent articles, and pagination is cursor-based. It omits anything about rate limits or the public-storefront-only restriction, but that constraint is documented in the schema.

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 what the tool returns, with the requirement and pagination note following. The parenthetical "(use cursor when paginated)" is slightly awkward phrasing but nothing is wasted.

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 no output schema, the description must carry the return-value burden, and it does name the key fields returned plus the list/pagination shape. For a read-only list tool with fully described parameters and rich annotations, that is nearly complete, though a clearer statement of the result envelope would close the remaining gap.

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 is already fully documented, and the description only restates the `store` requirement and the cursor's pagination role. It adds no format, range, or interaction semantics beyond the schema, making the baseline 3 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?

The description gives a specific verb and resource ("List a Shopify store's blogs") and adds the content scope (SEO, authors, recent articles), which lets an agent distinguish it from article-level siblings like shopify_articles_list. It stops short of explicitly naming a sibling or stating how it differs from shopify_articles_list or shopify_pages_list, so it is clear but not fully differentiated.

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?

It states the prerequisite ("Requires `store`") and gives a pagination cue ("use cursor when paginated"), which is useful operational guidance. However, it never says when to choose this tool over the article-listing or page-listing siblings, so usage is implied rather than directed.

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