Skip to main content
Glama
Sign In
shopify-multi-mcp

shopify-multi-mcp

by fledgeling-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Connect a Shopify store

connect_store

Add a Shopify store or sign in again when authentication expires by opening Shopify's browser approval page; reuse the store name to complete pending sign-in.

Instructions

Add a store, or sign in to one again when its session expired. Opens Shopify's own sign-in page in the user's browser (Shopify CLI "store auth"); the user must approve there, so tell them to look for the browser window. Returns within about 20 seconds; if approval is still pending, call it again with the same name to wait for the result.

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>"
    },
    "name": "connect_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelNoOptional human description, for example "Wholesale (NZ)".
storeYesShort name to refer to the store by, for example "au-retail". Reuse an existing name to sign in again.
domainNoThe store's permanent myshopify.com domain, for example "acme.myshopify.com". Required for a new store.
scopesNoAdmin API scopes to request. Defaults to: write_products, write_inventory, read_locations, write_orders, write_draft_orders, write_fulfillments, write_customers, write_discounts, write_content, write_metaobjects, write_files, write_publications, read_themes, read_reports, read_analytics.
read_onlyNoRequest read-only access and refuse mutations for this store.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.1/5.0
Behavior5/5

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

Adds behavior the annotations cannot convey: a browser window opens, the user must approve there, the call returns in ~20 seconds, and a retry with the same name polls for the result. These are the details an agent needs to avoid a spurious failure or a duplicate store.

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?

Three tight sentences, front-loaded with purpose, then flow, then timing/retry. The instruction to warn the user about the browser window is actionable rather than filler.

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?

Covers the whole interactive auth loop and its timing, which is the tricky part of this tool. It does not mention failure modes (user denies, bad domain, scope rejection), but with no output schema and full param coverage the gap is modest.

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 coverage is 100%, so the schema already explains label, store, domain, scopes, and read_only. The description only reinforces the 'same name to wait' reuse semantics, which the store parameter description already states.

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 concrete verb+resource ('Add a store') and even splits the two modes: first-time add vs. re-authenticating an expired session. It does not explicitly distinguish itself from siblings like list_stores, but the action is unambiguous.

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

Usage Guidelines4/5

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

Gives a clear trigger ('when its session expired') and operational guidance for the pending case (call again with the same name to wait for the result). No explicit exclusions or named alternatives, so it stops short of a 5.

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