Skip to main content
Glama

Check Shopify Connection

sirv_get_shopify_status
Read-onlyIdempotent

Check whether the connected Shopify store is valid and Studio access still works before pushing images or syncing products; returns connection status, shop domain, and reconnect flag.

Instructions

Check whether the workspace has a Shopify store connected and whether Studio's access to it still works.

Use it before sirv_push_image_to_shopify or sirv_sync_shopify_products. Do not use it to read products: use sirv_list_products. When needsReconnect is true, the user must reconnect the store in Studio.

Input: only the optional orgId; without it, the tool checks the workspace you signed in to.

Read-only: it changes nothing in Studio or in the store. Returns connected, valid, shop (the store domain), shopName and needsReconnect.

Credits: free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sirv_get_shopify_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description restates read-only while adding genuinely new context: the enumerated return fields (connected, valid, shop, shopName, needsReconnect), what needsReconnect implies for the user, and that the call costs no credits. The only redundancy is the read-only restatement, which the annotations already cover.

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?

Purpose is front-loaded, then usage/exclusions, then input, then behavior and return fields, then cost — each on its own line and each earning its place. No filler or marketing language.

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

Completeness5/5

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

For a single-optional-parameter diagnostic tool with no output schema and full annotation coverage, the description supplies everything an agent needs: when to call it, what it returns, how to interpret needsReconnect, and the cost profile.

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% for the single optional orgId parameter, and the description's note that omitting it checks the signed-in workspace largely mirrors the schema's own description. It adds no new syntax or format meaning, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific check with two precise conditions: whether a Shopify store is connected and whether Studio's access still works. It is immediately distinguishable from sibling tools like sirv_push_image_to_shopify and sirv_list_products without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit precondition usage ('Use it before sirv_push_image_to_shopify or sirv_sync_shopify_products'), an explicit exclusion ('Do not use it to read products') with the correct alternative named, and remediation guidance ('When needsReconnect is true, the user must reconnect the store in Studio').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.