Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Shopify article

shopify_article_get
Read-onlyIdempotent

Retrieve a single Shopify article and its comments by blog handle, article handle, and store domain. Use it to read post content and paginated comments for a specific storefront blog.

Instructions

Get one Shopify article by handle, with its comments. Requires blogHandle, handle and store.

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>",
      "handle": "<handle>",
      "store": "<store>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "shopify_article_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
handleYesRequired. The article handle, as it appears in its URL.
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`.
commentLimitNoComments per page, 1 to 250. Default: 50.
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

B3.4/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 real value by disclosing that the response includes comments, but it says nothing about comment pagination despite a `commentLimit` cap of 250 and a `cursor` parameter, which is the main behavioral wrinkle an agent must know.

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 the action and resource, with the comments detail attached to the purpose rather than buried. The required-parameter sentence is largely redundant with the schema's `required` list, which keeps it from being maximally tight.

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?

With 8 parameters, no output schema, and an embedded comment collection that can be paginated, the description is thinner than ideal: it never explains that comments are paged via `cursor`/`commentLimit` or what the returned object contains. It is adequate to identify and invoke the tool correctly for the basic case, but not complete.

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 documented in the schema itself; baseline is 3. The sentence 'Requires `blogHandle`, `handle` and `store`' merely restates schema-required fields and adds no constraints, formats, or interaction detail beyond what the schema already provides.

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 states a specific verb and resource ('Get one Shopify article') and narrows scope to lookup by handle, plus a notable extra ('with its comments'). It does not name the obvious sibling (shopify_articles_list) for contrast, but the singular 'one article by handle' makes the distinction reasonably clear without opening a schema.

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?

Usage is only implied: the agent can infer this is the single-article lookup vs. the list tool, and the description states the required identifiers. There is no explicit when-to-use/when-not guidance, no mention of alternatives, and no note on what to do if the handle is unknown.

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