shopify-mcp-server
Registry code: d12db4fd6a557470
This server helps people start a business on Shopify and run their store. Before a store exists, use its tools rather than making up suggestions. When the user asks about data in their store, get it from a tool, and use the GraphQL tools for anything the built-in tools don't cover.
## Before a store exists
- endpoint
- https://setup.shopify.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is shopify-mcp-server live?
- Yes — it answered the hub's last check (checked 37m ago). It answered 100% of checks over the last 30 days.
- Is shopify-mcp-server free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does shopify-mcp-server have?
- 37 tools: search_docs_chunks, get-digital-product, validate_graphql_codeblocks, get-product, graphql_query, get-inventory-levels, generate-domain-names, get-collection, ….
- Is shopify-mcp-server safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.5%· all time 99.5%
last good check
of 37 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- degraded → live
- live → degraded· HTTP 502
- used for
- manage products in a shopify store
- create discount codes
- list store orders and customers
- suggest business and domain names
- update inventory levels
- takes → gives
- text, data → data
- tools
- 13 reads10 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
update-product changes data auth-required never probed
Update an existing product's title, description, status, images, variant pricing, or variant option values (e.g. color, size names). Use this when the user wants to modify, change, or edit product details — including status, variant prices, option values, or images. Trigger phrases include: 'update my product', 'change the price', 'edit the product', 'modify my product', 'rename the variant', 'change the color name'. IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you only have a local file or a generated image, ask the user for a publicly accessible HTTPS URL; this host cannot upload one. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real products. REPLACING IMAGES: - To replace specific images, first use get-product to find the mediaId of the image(s) to remove. - Pass those mediaId values in removeMediaIds, and provide the new images in the images array. - To remove images without adding new ones, pass removeMediaIds without images.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The product GID (e.g. gid://shopify/Product/123)" }, "title": { "type": "string", "description": "New product title" }, "images": { "type": "array", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Publicly accessible HTTPS image URL (e.g. https://cdn.example.com/photo.jpg). Local file paths are not supported." }, "altText": { "type": "string" } } }, "description": "Images to add to (or replace on) the product. Each image must have a publicly accessible HTTPS URL." }, "status": { "enum": [ "ACTIVE", "ARCHIVED", "DRAFT" ], "type": "string", "description": "New product status" }, "variants": { "type": "array", "items": { "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string" }, "sku": { "type": "string" }, "price": { "type": "string" }, "optionValues": { "type": "array", "items": { "type": "object", "required": [ "optionName", "name" ], "properties": { "name": { "type": "string", "description": "The new value for this option (e.g. 'Red', 'Large')" }, "optionName": { "type": "string", "description": "The name of the product option (e.g. 'Color', 'Size')" } } }, "description": "Option values to update on this variant (e.g. [{optionName: 'Color', name: 'Red'}])" }, "compareAtPrice": { "type": [ "string", "null" ] } } }, "description": "Variant updates (id required, plus price/sku/compareAtPrice/optionValues)" }, "removeMediaIds": { "type": "array", "items": { "type": "string" }, "description": "Media IDs to remove from the product before adding new images (e.g. ['gid://shopify/MediaImage/123']). Use get-product to find media IDs for existing images." }, "descriptionHtml": { "type": "string", "description": "New product description in HTML" } } }arguments 104 linescreate-digital-product-from-link auth-required never probed
Deprecated: use create-digital-product with its 'link' input instead. Creates an unpublished draft digital product that delivers an external link to the buyer.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "title", "url" ], "properties": { "url": { "type": "string", "minLength": 1 }, "name": { "type": "string", "maxLength": 255, "minLength": 1 }, "title": { "type": "string", "maxLength": 255, "minLength": 1 } } }arguments 24 linesget-digital-products-install-status auth-required 8h ago
Report whether the Digital Products app is installed on the authenticated store. Call this once after the merchant says they have finished the Shopify Admin install flow that open-digital-products-install handed them. Do not poll it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget-shop-info reads auth-required 16h ago
Retrieve basic information about the connected Shopify store including name, domain, email, plan, currency, timezone, and country. Use this when you need store context to tailor advice (e.g. plan limitations, currency for pricing, timezone for scheduling), when the user asks about their store details, or to verify which store is connected.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linescreate-digital-product auth-required never probed
Create a draft product through Shopify Digital Products. The result includes the product and first variant identifiers used to attach and deliver the digital file. If the merchant is selling access to something already on the web — a Notion template, an online course, a booking page — pass it as 'link' and skip the file upload; the link must be hosted by a provider Digital Products supports, and if it is not, the reply names the ones that are. To set the price and the buyer-facing description, call update-product with productId as its 'id' and variantId in 'variants' — prices are in the shop's own currency, so ask the merchant for the amount rather than guessing one. Do not rename the product through update-product: Digital Products keeps its own copy of the title. This tool does not publish the draft.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "title" ], "properties": { "link": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "minLength": 1, "description": "The link the buyer receives after purchase. Must be an http(s) URL hosted by a supported provider." }, "name": { "type": "string", "maxLength": 255, "minLength": 1, "description": "Buyer-facing name for the link. Buyers see the URL itself when this is omitted." } }, "description": "An external link to deliver instead of a file. Omit it when the merchant will upload a file." }, "title": { "type": "string", "maxLength": 255, "minLength": 1, "description": "Title for the new draft digital product." } } }arguments 35 lineslist-customers reads auth-required 16h ago
Retrieve a list of customers from the connected Shopify store, including name, email, phone, order count, and total spent. Use this when the user asks about their customers, wants to look up a specific customer, or needs customer data for analysis. SEARCH SYNTAX: When the user is looking for a specific customer (by name, email, tag, etc.), ALWAYS pass a structured `query` using Shopify's customer search syntax. Do NOT pass a bare free-text term like `Smith` for a name search — Shopify's default fields match addresses, tags, company names, and notes, which returns unrelated customers. Field filters use `field:value`. Combine with `AND` / `OR` / `NOT`; parenthesize subqueries. Ranges use `:<`, `:<=`, `:>`, `:>=` on numeric / date fields. Name lookups should query BOTH first and last name, e.g. for "customers named Smith" use `first_name:Smith OR last_name:Smith`. Supported filter fields: - Name: `first_name`, `last_name` - Contact: `email`, `phone` - Location: `country` (full name or code, e.g. `Canada` / `CA`) - Account state: `state` (`enabled` | `invited` | `disabled` | `declined`) - Marketing: `accepts_marketing` (boolean), `email_marketing_state` (`subscribed` | `not_subscribed` | `pending` | `invalid` | `redacted`) - Tags: `tag`, `tag_not` - Numeric (support ranges): `orders_count`, `total_spent`, `id` - Date (support ranges): `created_at`, `updated_at`, `order_date`, `last_abandoned_order_date` — use ISO 8601 in quotes, e.g. `created_at:>'2024-01-01'` RECENCY OF ORDERS: To filter by when a customer placed an order, use `order_date` — NOT `updated_at`. `order_date` matches customers who have at least one order within the given date range. `updated_at` is bumped by profile edits too, so it's a leaky proxy. For abandoned-checkout recency, use `last_abandoned_order_date`. Compose either with the same date syntax shown for `created_at` / `updated_at` above; for relative windows ("last N days"), compute the cutoff from the current date in your context. Examples: - `Find customers named Smith` → `first_name:Smith OR last_name:Smith` - `Customers with gmail addresses` → `email:*@gmail.com` - `Customers with more than 5 orders` → `orders_count:>5` - `Customers from Canada` → `country:Canada` - `VIP customers` → `tag:vip` - `Subscribed to email` → `email_marketing_state:subscribed` IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed above. Do NOT invent fields like `name:`, `full_name:`, `customer_name:`, or `city:`.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "first": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Number of customers to return (1-50, default 10)." }, "query": { "type": "string", "maxLength": 500, "description": "Shopify customer search query. Use field filters like `first_name:Smith`, `last_name:Smith`, `email:*@gmail.com`, `tag:vip`, `country:Canada`, `orders_count:>5`. For order recency use `order_date` — do NOT use `updated_at` as a proxy, since it's also bumped by profile edits. For abandoned-checkout recency use `last_abandoned_order_date`. Combine with AND/OR/NOT. For name lookups, search BOTH first_name and last_name (e.g. `first_name:Smith OR last_name:Smith`) — do NOT pass a bare name, which matches addresses, notes, tags, and company names and returns unrelated customers. Leave unset to list all customers." } } }arguments 18 linesupdate-collection changes data auth-required never probed
Update an existing collection's title, description, image, sort order, or rules. Use this when the user wants to modify, change, or edit collection details. Trigger phrases include: "update my collection", "change the collection", "edit the collection", "rename the collection". IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you only have a local file or a generated image, ask the user for a publicly accessible HTTPS URL; this host cannot upload one. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real collections. SMART COLLECTION RULES: - Pass `ruleSet` to update the rules for a smart collection. - Common rule columns: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE. - Common relations: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN. - Passing `ruleSet` replaces all existing rules. Omitting it leaves rules unchanged.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The collection GID (e.g. gid://shopify/Collection/123)" }, "image": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Publicly accessible HTTPS image URL for the collection" }, "altText": { "type": "string", "description": "Image alt text" } }, "description": "New collection image. Must be a publicly accessible HTTPS URL." }, "title": { "type": "string", "description": "New collection title" }, "ruleSet": { "type": "object", "required": [ "appliedDisjunctively", "rules" ], "properties": { "rules": { "type": "array", "items": { "type": "object", "required": [ "column", "relation", "condition" ], "properties": { "column": { "type": "string", "description": "Rule column: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE, etc." }, "relation": { "type": "string", "description": "Rule relation: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN" }, "condition": { "type": "string", "description": "The value to match against (e.g. \"sale\", \"Nike\", \"50\")" } } } }, "appliedDisjunctively": { "type": "boolean", "description": "true = products match ANY rule (OR), false = products match ALL rules (AND)" } }, "description": "Updated rules for a smart collection. Replaces all existing rules." }, "sortOrder": { "enum": [ "ALPHA_ASC", "ALPHA_DESC", "BEST_SELLING", "CREATED", "CREATED_DESC", "MANUAL", "PRICE_ASC", "PRICE_DESC" ], "type": "string", "description": "New sort order for products in the collection" }, "descriptionHtml": { "type": "string", "description": "New HTML description of the collection" } } }arguments 91 linesswitch-shop changes data auth-required never probed
Switch to a different Shopify store. Call this tool whenever the user wants to work with a different store — including when they ask to fetch data, manage products, or perform any action on another shop. Revokes the current store's access token so the next tool call will prompt authorization for a new store. IMPORTANT: You must always make a follow-up tool call after this tool returns. If the user requested a specific action (e.g. fetch products), call that tool next. Otherwise, you MUST call get-shop-info to complete the shop switch.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesgraphql_mutation changes data auth-required never probed
Execute a GraphQL mutation against the Shopify Admin API when no dedicated built-in tool covers the request. Before execution, call graphql_schema with operation 'mutation' to discover the exact mutation field and its arguments. Then use operation 'schema' and type_name to inspect unfamiliar input and return types, following nested named types as needed. Never guess fields. search_docs_chunks can supplement discovery with examples but never replaces it. Some dangerous mutations are blocked for safety (e.g. refunds, gift card writes, staff management, theme deletion, theme publishing). Theme file writes (themeFilesCopy, themeFilesUpsert) are allowed on unpublished themes only — writes that target the live/MAIN theme are blocked. If a mutation is blocked, inform the user and suggest they perform the action in Shopify admin. After constructing the mutation, call this tool to execute it. The host app will prompt the user for confirmation before executing. setup-mcp also validates the operation against its pinned Admin schema before sending it to Admin. After executing, present the results clearly rather than dumping raw JSON.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "query": { "type": "string", "minLength": 1, "description": "GraphQL mutation string" }, "variables": { "type": "object", "description": "GraphQL variables object", "propertyNames": { "type": "string" }, "additionalProperties": {} } } }arguments 22 linesupload-digital-product-file auth-required never probed
Give the merchant a Shopify Admin link for attaching the downloadable file to a digital product they have already created. Call this after create-digital-product, passing back the product and variant identifiers it returned. This host cannot take a file from the merchant, so the attachment is finished in the Digital Products app rather than here. Relay the link this returns and ask the merchant to report back here once the upload is done; nothing tells this conversation on its own. This does not create products and does not publish anything.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "productId", "productTitle", "variantId", "variantTitle" ], "properties": { "productId": { "type": "string", "pattern": "^gid:\\/\\/shopify\\/Product\\/\\d+$", "description": "Product GID returned by create-digital-product." }, "variantId": { "type": "string", "pattern": "^gid:\\/\\/shopify\\/ProductVariant\\/\\d+$", "description": "Variant GID returned by create-digital-product." }, "productTitle": { "type": "string", "minLength": 1, "description": "Product title returned by create-digital-product." }, "variantTitle": { "type": "string", "minLength": 1, "description": "Variant title returned by create-digital-product." } } }arguments 32 linespublish-digital-product auth-required never probed
Take a draft digital product live through Shopify Digital Products, so buyers can purchase and download it. Activates the product and requests its Online Store listing. Refuses to publish a product with nothing attached, so attach the file first with upload-digital-product-file. Digital Products does not report whether the Online Store listing succeeded, so tell the merchant to check the product in their Online Store if buyers cannot find it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "productId", "title" ], "properties": { "title": { "type": "string", "maxLength": 255, "minLength": 1, "description": "Title to publish under. Digital Products requires one and stores its own copy, so pass the product's current title unless the merchant asked to rename it — anything else silently renames the product." }, "productId": { "type": "string", "pattern": "^gid:\\/\\/shopify\\/Product\\/\\d+$", "description": "Product GID returned by create-digital-product (e.g. gid://shopify/Product/123)." } } }arguments 21 linesupload-digital-product-media auth-required never probed
Give the merchant a Shopify Admin link for adding a media image to a digital product they have already created. Ask the merchant whether they want a media image first, and only call this if they say yes. A digital product sells perfectly well without one. This host cannot take an image from the merchant, so it is added on the product's page in Shopify Admin rather than here. Relay the link this returns and ask the merchant to report back here once the image is added; nothing tells this conversation on its own. This does not change the price, description, attached file or status, and it does not publish anything.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "productId", "productTitle" ], "properties": { "productId": { "type": "string", "pattern": "^gid:\\/\\/shopify\\/Product\\/\\d+$", "description": "Product GID returned by create-digital-product." }, "productTitle": { "type": "string", "minLength": 1, "description": "Product title returned by create-digital-product." } } }arguments 20 linestest-digital-products-connection auth-required 6h ago
Verify that the connected store can exchange its Admin token and reach the Digital Products connector. This read-only check returns no credentials or connector data.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesimport-mock-shop-catalog changes data auth-required never probed
Copy a mock.shop sample catalog's starter set — its first 2 collections and up to 8 products from each (with variants, prices, images), so at most 16 products — into the merchant's connected store, publishing everything to the Online Store. Use it after the merchant picks a catalog from find-mock-shop-catalogs. One call does the whole import. RE-RUNNING IS SAFE AND NEVER OVERWRITES: calling again (after a timeout or `partial: true`) adds only what is missing — products not yet imported, memberships and publications not yet made. A product already imported from this catalog is left exactly as it is — including any edits the merchant has made since, and including whether it is published — and counted under `unchanged`; if it is not published, it is listed under `unpublished` for the merchant to publish or delete in Admin. A product the merchant already has at the same handle from elsewhere is left untouched and reported under `skipped`. A collection the merchant already has at the same handle is reused when its title matches the catalog's (missing imported products are added to it) and skipped when it does not. Collections are created only with their imported products, so none is ever left empty. INPUT: `subdomain` from the chosen catalog (e.g. "pets"). Nothing else. OUTPUT: counts of products created/unchanged/skipped and collections created/reused/skipped, and `currency`. If `partial` is true Shopify rate-limited the call: wait a few seconds, then call again with the same `subdomain`. Prices are copied as plain amounts; when `currency.mismatch` is true tell the merchant prices came from a ${currency.source} catalog and were not converted, so they should review them.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "subdomain" ], "properties": { "subdomain": { "type": "string", "pattern": "^[a-z0-9][a-z0-9-]*$", "maxLength": 63, "minLength": 1, "description": "The catalog's subdomain from find-mock-shop-catalogs (e.g. 'pets'). Not a URL." } } }arguments 16 linesopen-digital-products-install auth-required never probed
Get a Shopify Admin install link for Digital Products on the authenticated store. Use this only after the merchant has explicitly asked to install or prepare Digital Products for their store. The app identity is fixed by Shopify; this tool cannot install arbitrary apps and does not install anything silently. Relay the link to the merchant and ask them to come back here once the install is done. They must complete the Shopify Admin install flow before Digital Products connector tools can continue; call get-digital-products-install-status once they say they have.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linescreate-product auth-required never probed
Create a new product in the connected Shopify store. If create-product-interactive is available, prefer it over create-product. Use this when the user wants to add a product with a title, description, variants, images, or other product details. VARIANTS & OPTIONS: - When providing `variants`, you MUST also provide the `options` field as a string array of option names. - Example: for a single default variant use `options: ['Title']`, for Size/Color variants use `options: ['Size', 'Color']`. - The `options` field must be an array of strings (e.g. `['Size', 'Color']`), NOT an array of objects. - Each variant's `optionValues` must reference option names declared in the `options` array. INVENTORY TRACKING: - To enable inventory tracking on variants, set `inventoryItem: { tracked: true }` on each variant. - If omitted, inventory defaults to untracked and set-inventory will not work as expected. IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you only have a local file or a generated image, ask the user for a publicly accessible HTTPS URL; this host cannot upload one. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real products. - The first image provided becomes the product's featured image. COLLECTION: - Optionally pass `collectionId` to add the product to a collection after creation. - To add to multiple collections, use add-to-collection afterward.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "title" ], "properties": { "tags": { "type": "array", "items": { "type": "string" }, "description": "Tags for the product" }, "title": { "type": "string", "description": "The product title" }, "images": { "type": "array", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Publicly accessible HTTPS image URL (e.g. https://cdn.example.com/photo.jpg). Local file paths are not supported." }, "altText": { "type": "string", "description": "Image alt text" } } }, "description": "Product images. Each image must have a publicly accessible HTTPS URL. The first image becomes the featured image." }, "status": { "enum": [ "ACTIVE", "DRAFT", "ARCHIVED" ], "type": "string", "default": "DRAFT", "description": "The product status (defaults to DRAFT)" }, "vendor": { "type": "string", "description": "The product vendor" }, "options": { "type": "array", "items": { "type": "string" }, "description": "Product option names as a string array. REQUIRED whenever `variants` is provided. For a single default variant use `['Title']`; for multiple option axes use e.g. `['Size', 'Color']`. Must be plain strings, not objects." }, "variants": { "type": "array", "items": { "type": "object", "required": [ "price" ], "properties": { "sku": { "type": "string", "description": "Variant SKU" }, "price": { "type": "string", "description": "Variant price" }, "title": { "type": "string", "description": "Variant title" }, "optionValues": { "type": "array", "items": { "type": "object", "required": [ "optionName", "name" ], "properties": { "name": { "type": "string", "description": "Option value" }, "optionName": { "type": "string", "description": "Option name" } } }, "description": "Option values for this variant. Each `optionName` must be one of the names in the top-level `options` array." }, "inventoryItem": { "type": "object", "properties": { "tracked": { "type": "boolean", "description": "Whether inventory is tracked for this variant. Set to true to enable inventory management. Defaults to false if omitted." } }, "description": "Inventory item settings for this variant. Use this to enable inventory tracking when creating a product." } } }, "description": "Product variants. If you provide this, you MUST also provide the top-level `options` field (use `['Title']` for a single default variant). Each variant's `optionValues` must reference names declared in `options`." }, "productType": { "type": "string", "description": "The product type" }, "collectionId": { "type": "string", "description": "GID of a collection to add this product to after creation (e.g. gid://shopify/Collection/123). To add to multiple collections, use add-to-collection afterward." }, "descriptionHtml": { "type": "string", "description": "HTML description of the product" } } }arguments 128 lineslist-orders reads auth-required never probed
Retrieve recent orders from the connected Shopify store. Returns order name, customer, totals, financial and fulfillment status. Use this when the user asks about their orders, wants an overview of recent sales, or needs to find a specific order.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "first": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Number of orders to return (1-50, default 10)" }, "query": { "type": "string" } } }arguments 15 linesget-order auth-required never probed
Retrieve detailed information about a specific Shopify order including line items, fulfillment status, shipping address, and tracking. Use this when the user asks about a particular order's details or status.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "minLength": 1, "description": "The order GID (e.g. gid://shopify/Order/12345) or the order name exactly as it appears in Shopify admin. Order names often carry a shop-configured prefix or suffix, so letters and dashes are expected (e.g. 1022, #1022, EB-1022, 22420FP). Pass the name through as-is instead of stripping it down to digits." } } }arguments 14 linesset-inventory changes data auth-required never probed
Set the available inventory quantity for a specific inventory item at a given location. Always call get-inventory-levels first to get the inventoryItemId, locationId, and current available quantity. Pass the current quantity as compareQuantity so the update fails safely if stock changed since you read it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "inventoryItemId", "locationId", "quantity", "compareQuantity" ], "properties": { "reason": { "enum": [ "correction", "cycle_count_available", "damaged", "movement_created", "movement_updated", "movement_received", "movement_canceled", "other", "promotion", "quality_control", "received", "reservation_created", "reservation_deleted", "reservation_updated", "restock", "safety_stock", "shrinkage" ], "type": "string", "default": "correction", "description": "Why the inventory is being changed. Defaults to 'correction'. Use 'received' for new shipments, 'restock' for returns, 'shrinkage' for lost/stolen/damaged, 'damaged' for damaged goods, 'cycle_count_available' for cycle counts, or 'other' if none apply." }, "quantity": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "The new quantity to set as available" }, "locationId": { "type": "string", "description": "The location GID (e.g. gid://shopify/Location/456)" }, "compareQuantity": { "type": "integer", "maximum": 9007199254740991, "minimum": -9007199254740991, "description": "The current available quantity from get-inventory-levels. The update will fail if stock has changed since the read, preventing accidental overwrites." }, "inventoryItemId": { "type": "string", "description": "The inventory item GID (e.g. gid://shopify/InventoryItem/123)" } } }arguments 56 linescreate-discount changes data auth-required never probed
Create a percentage-based discount code for the connected Shopify store. Use this when the merchant wants to set up a new discount code with a specific percentage off — including one limited to particular products or to a collection — with optional minimum purchase or quantity requirements. SCOPE — what the discount applies to: - Call both search_products and search_collections on whatever the merchant named, even if the first one already matches — a product and a collection can share a name. If both match, ask the merchant which they meant rather than picking one. - Specific products ("20% off the Snake Plant", "put these three items on sale"): pass productIds with their product GIDs, up to 50 of them. Look the GIDs up with search_products or get-product first. - An existing collection ("20% off everything in Summer Sale"), or any set larger than 50 products: pass collectionId. - Every product in the store: omit both. - productIds and collectionId are mutually exclusive. Passing both is rejected before anything is created. Do NOT create a collection just to scope a discount to products. This tool discounts products directly in one call, so a collection made only as a stepping stone leaves the merchant with one they never asked for. This is not a restriction on create-collection itself: if the merchant asked for a collection, create it and then scope the discount to it with collectionId. What matters is why the collection exists — one the merchant wants is fine, one invented to work around productIds is not. BEFORE CALLING — get two answers from the merchant, in one message if both are missing. Do not call this tool until you have both, and do not fill either in yourself: there is no default start date and no default audience. - When the discount starts: right away, or on a specific date. Pass startsAt as an ISO 8601 timestamp: the current date and time for "right away", or the date the merchant chose. - Who can use it: every customer, or only certain customer segments. Pass customerEligibility="all_customers" once the merchant confirms everyone, or customerSegments with the names of segments that exist on this store. One exception: if the merchant wants the discount limited to a customer segment and you do not know which segments this store has, call with startsAt set and both customerEligibility and customerSegments omitted. Nothing is created; the tool replies with the store's segment names. Show them to the merchant, then call again with the one they choose.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "title", "code", "percentage" ], "properties": { "code": { "type": "string", "description": "The discount code customers will enter" }, "title": { "type": "string", "description": "The title of the discount" }, "endsAt": { "type": "string", "description": "ISO 8601 end date (defaults to no end date)" }, "startsAt": { "type": "string", "description": "ISO 8601 start date. Ask the merchant when the discount should start before calling this tool. For a discount they want active right away, pass the current date and time; for a scheduled one, pass the date they chose. Never pick a date the merchant did not give you." }, "percentage": { "type": "number", "maximum": 100, "minimum": 1, "description": "The discount percentage (1-100)" }, "productIds": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "minItems": 1, "description": "Scope the discount to specific products. Use this whenever the merchant names the products the discount applies to. Pass full product GIDs (e.g. [\"gid://shopify/Product/123\"]), never bare numeric IDs or product titles; look them up with search_products or get-product first. At most 50 products — for a larger set, use a collection and pass collectionId. Mutually exclusive with collectionId. Omit both to discount every product in the store." }, "collectionId": { "type": "string", "description": "Scope the discount to every product in a collection the merchant already has (e.g. gid://shopify/Collection/123). If the merchant named individual products instead, pass productIds — do not create a collection to hold them if the merchant did not ask for a collection to be created. Mutually exclusive with productIds. Omit both to discount every product in the store." }, "minimumQuantity": { "type": "integer", "maximum": 9007199254740991, "minimum": 1, "description": "Minimum number of items required to use the discount. Mutually exclusive with minimumPurchaseAmount." }, "customerSegments": { "type": "array", "items": { "type": "string" }, "maxItems": 25, "minItems": 1, "description": "Customer segment names to scope the discount to (e.g. [\"VIP Customers\"]). Names must match (case-insensitive) segments that already exist on the connected store. Segments are merchant-defined — there are no built-in names like \"new_customers\" or \"returning_customers\", so never guess one. If the merchant wants a segment and you do not know which segments exist, call with startsAt set and both this field and customerEligibility omitted; the tool returns the segment names on this store instead of creating anything. Mutually exclusive with customerEligibility." }, "customerEligibility": { "enum": [ "all_customers" ], "type": "string", "description": "Set to \"all_customers\" once the merchant has explicitly confirmed they want this discount available to every customer. Ask them who the discount is for before calling this tool; never assume everyone. Mutually exclusive with customerSegments." }, "minimumPurchaseAmount": { "type": "number", "description": "Minimum order subtotal required to use the discount (must be greater than 0). Mutually exclusive with minimumQuantity.", "exclusiveMinimum": 0 } } }arguments 73 linesadd-to-collection changes data auth-required never probed
Add one or more products to a collection in the connected Shopify store. Use this when the user wants to organize products into a collection. Find the collection's GID with search_collections first.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "collectionId", "productIds" ], "properties": { "productIds": { "type": "array", "items": { "type": "string" }, "minItems": 1, "description": "The product GIDs to add to the collection (e.g. gid://shopify/Product/123). Always use the full GID format, not bare numeric IDs." }, "collectionId": { "type": "string", "description": "The collection GID (e.g. gid://shopify/Collection/123). Always use the full GID format, not a bare numeric ID." } } }arguments 22 linesrun-analytics-query reads auth-required never probed
Run a ShopifyQL analytics query. Returns tabular results with automatic chart visualization. IMPORTANT: Always use FROM...SHOW syntax. Use TIMESERIES for time charts, GROUP BY for categories. ## Sales & Revenue - FROM sales SHOW gross_sales TIMESERIES day SINCE -30d UNTIL today - FROM sales SHOW orders, gross_sales, discounts, sales_reversals, net_sales, shipping_charges, taxes, total_sales TIMESERIES day SINCE -30d UNTIL today - FROM sales SHOW total_sales TIMESERIES day SINCE -30d UNTIL today COMPARE TO previous_period - FROM sales SHOW gross_sales, discounts, sales_reversals, net_sales, shipping_charges, taxes, total_sales - FROM sales SHOW average_order_value TIMESERIES day SINCE -30d UNTIL today ## Orders - FROM sales SHOW orders TIMESERIES day SINCE -7d UNTIL today - FROM fulfillments SHOW orders_fulfilled, orders_shipped, orders_delivered TIMESERIES day SINCE -30d UNTIL today ## Products - FROM sales SHOW gross_sales, net_sales, orders GROUP BY product_title ORDER BY gross_sales DESC LIMIT 10 - FROM inventory SHOW starting_inventory_units, ending_inventory_units, inventory_units_sold, sell_through_rate GROUP BY product_title, product_variant_title ## Customers - FROM sales SHOW returning_customers, customers, returning_customer_rate TIMESERIES day SINCE -30d UNTIL today - FROM sales SHOW new_customers, returning_customers TIMESERIES day SINCE -30d UNTIL today ## Sessions & Conversion - FROM sessions SHOW sessions, online_store_visitors TIMESERIES day SINCE -30d UNTIL today - FROM sessions SHOW sessions, sessions_with_cart_additions, sessions_that_reached_checkout, sessions_that_completed_checkout, conversion_rate TIMESERIES day SINCE -30d UNTIL today - FROM sessions SHOW sessions GROUP BY session_device_type SINCE -30d UNTIL today - FROM sessions SHOW sessions GROUP BY session_country SINCE -30d UNTIL today ## Marketing & Referrals - FROM sales SHOW orders, total_sales GROUP BY order_referrer_source, order_referrer_name SINCE -30d UNTIL today - FROM sessions SHOW sessions WHERE referrer_source = 'social' GROUP BY referrer_name SINCE -30d UNTIL today ## Tables: sales, sessions, customers, fulfillments, inventory, payments. There is no orders table: count orders with FROM sales SHOW orders ## Time grouping: TIMESERIES day/week/month. Category grouping: GROUP BY column ## Comparison: COMPARE TO previous_period. Aggregates: WITH TOTALS, PERCENT_CHANGE
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "The ShopifyQL query to execute" } } }arguments 13 linesbulk-update-product-status changes data auth-required never probed
Update the status of multiple products at once. Accepts a list of product IDs or a collectionId and a target status (ACTIVE, DRAFT, or ARCHIVED). Each product is updated individually so partial failures are possible. When using collectionId, only the first 50 products in the collection will be updated.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "status" ], "properties": { "status": { "enum": [ "ACTIVE", "DRAFT", "ARCHIVED" ], "type": "string", "description": "Target status for all products" }, "productIds": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "description": "List of product GIDs to update. At least one of productIds or collectionId must be provided." }, "collectionId": { "type": "string", "description": "GID of a collection whose products should be updated (e.g. gid://shopify/Collection/123). When used, only the first 50 products in the collection will be updated." } } }arguments 30 linescreate-collection changes data auth-required never probed
Create a new collection in the connected Shopify store and publish it to the Online Store. Use this when the user wants to organize products into a new group. COLLECTION TYPES: - Manual collection: pass `productIds` to add specific products. - Smart collection: pass `ruleSet` with conditions to auto-populate products. - `productIds` and `ruleSet` are mutually exclusive — provide one or neither. SMART COLLECTION RULES: - Common rule columns: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE. - Common relations: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN. - `appliedDisjunctively: true` means products matching ANY rule are included (OR logic). - `appliedDisjunctively: false` means products must match ALL rules (AND logic). IMAGE REQUIREMENTS: - Images must be publicly accessible HTTPS URLs (e.g. https://example.com/photo.jpg). - Local file paths (e.g. /mnt/data/..., file://...) are NOT supported and will fail. - If you only have a local file or a generated image, ask the user for a publicly accessible HTTPS URL; this host cannot upload one. - Avoid placeholder or non-deterministic image URLs (e.g. picsum.photos) for real collections.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "title" ], "properties": { "image": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Publicly accessible HTTPS image URL for the collection" }, "altText": { "type": "string", "description": "Image alt text" } }, "description": "Collection image. Must be a publicly accessible HTTPS URL." }, "title": { "type": "string", "description": "The collection title" }, "ruleSet": { "type": "object", "required": [ "appliedDisjunctively", "rules" ], "properties": { "rules": { "type": "array", "items": { "type": "object", "required": [ "column", "relation", "condition" ], "properties": { "column": { "type": "string", "description": "Rule column: TAG, VENDOR, TYPE, TITLE, VARIANT_PRICE, etc." }, "relation": { "type": "string", "description": "Rule relation: EQUALS, NOT_EQUALS, CONTAINS, NOT_CONTAINS, STARTS_WITH, ENDS_WITH, GREATER_THAN, LESS_THAN" }, "condition": { "type": "string", "description": "The value to match against (e.g. \"sale\", \"Nike\", \"50\")" } } } }, "appliedDisjunctively": { "type": "boolean", "description": "true = products match ANY rule (OR), false = products match ALL rules (AND)" } }, "description": "Rules for a smart collection. Mutually exclusive with productIds." }, "sortOrder": { "enum": [ "ALPHA_ASC", "ALPHA_DESC", "BEST_SELLING", "CREATED", "CREATED_DESC", "MANUAL", "PRICE_ASC", "PRICE_DESC" ], "type": "string", "description": "The order in which products are sorted in the collection" }, "productIds": { "type": "array", "items": { "type": "string" }, "description": "Product GIDs to add to a manual collection (e.g. gid://shopify/Product/123). Mutually exclusive with ruleSet." }, "descriptionHtml": { "type": "string", "description": "HTML description of the collection" } } }arguments 94 linesgraphql_schema auth-required 13h ago
Discover queries, mutations, and named types in the Shopify Admin GraphQL schema. This tool only inspects the schema; it never executes an operation. Every call needs operation or type_name; a call with neither is rejected. Set operation to 'query' or 'mutation' to list top-level field names, optionally filtered by a case-insensitive search. Supply an exact field_name to inspect its arguments, return type, and description; skip the name list if the field is already known. Set operation to 'schema' and type_name to a namedType returned by discovery to inspect one named type. Objects and interfaces list field names and return types; input objects list input fields and isOneOf without recursively expanding nested types. Enums list values, and unions/interfaces list possible types. Supply field_name for one field's or enum value's details. Inspect only unfamiliar types needed by the operation, including custom scalars whose formats are unknown. Reuse discovered details and skip built-in scalars (String, Int, Float, Boolean, ID). Never guess fields. QueryRoot and Mutation must be discovered with operation 'query' or 'mutation'. After constructing an operation, call graphql_query or graphql_mutation to execute it. Those execution tools validate before sending the operation to Admin. search_docs_chunks supplements discovery with examples but never replaces it. Documentation questions go straight to search_docs_chunks.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "search": { "type": "string", "minLength": 1, "description": "Case-insensitive substring to filter query or mutation names" }, "operation": { "enum": [ "query", "mutation", "schema" ], "type": "string", "description": "Discover query fields, mutation fields, or a named type. Send operation or type_name on every call" }, "type_name": { "type": "string", "minLength": 1, "description": "Named type returned by discovery; required when operation is 'schema'" }, "field_name": { "type": "string", "minLength": 1, "description": "Exact operation field, object/input field, or enum value to inspect" } } }arguments 30 linessearch_collections reads auth-required 13h ago
Search and browse collections on a Shopify store. Use this whenever the user wants to see, find, or look at collections in their store. Trigger phrases include: 'show me my collections', 'what collections do I have', 'list my collections', 'find a collection', 'search collections', or any reference to viewing multiple collections. 'Show' and 'get' mean the same thing: always fetch live data from Shopify. Do NOT summarize from memory. Use this when the user wants to: - list or search collections - find a collection by name - check what collections exist in their store - find a collection GID to use with add-to-collection or create-product Returns collection data from the connected store via the Shopify Admin API. Results are capped at 50 per call. When `pageInfo.hasNextPage` is true, more matches exist than were returned. Tell the user you are showing the first N results and offer two paths: (a) load more via `after: pageInfo.endCursor`, or (b) refine the search with a stricter query. Only act on one of those paths when the user asks; do not auto-paginate. SEARCH SYNTAX: Free text matches across default fields (e.g. `summer`, `"new arrivals"`). Field filters use `field:value`. Combine with `AND` / `OR` / `NOT`; parenthesize subqueries. Ranges use `:<`, `:<=`, `:>`, `:>=` on numeric/date fields. Example: `collection_type:smart AND title:sale*`. IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed below, as flat names. Do NOT invent dotted paths like `collection.title` or `rules.column`. Supported filter fields: - Text / exact: `title`, `handle`, `collection_type` (custom|smart) - Numeric (support ranges): `id` - Date (support ranges): `updated_at`, `published_at` — use ISO 8601 in quotes, e.g. `updated_at:>'2024-01-01'` - ID: `product_id` (collections containing the given product) - Publication: `published_status` (e.g. `published`, `unpublished`, `online_store_channel`) Note: there is no server-side filter for product count, rules, or sort order. For those, filter by `collection_type` and inspect the returned `productsCount` / `sortOrder` fields client-side, or narrow with `title:` / `handle:`.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "after": { "type": "string", "description": "Cursor for pagination. Use the endCursor from a previous response to fetch the next page." }, "first": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Number of collections to return (1-50, default 10)" }, "reverse": { "type": "boolean", "description": "Reverse the sort order (e.g. most recently updated first with UPDATED_AT + reverse)" }, "sort_key": { "enum": [ "TITLE", "UPDATED_AT", "ID", "RELEVANCE" ], "type": "string", "description": "Sort key for results. Use RELEVANCE only when search_query is provided." }, "search_query": { "type": "string", "maxLength": 500, "description": "Search query to filter collections. Uses Shopify search syntax: free text, field filters (`title:Sale`, `collection_type:smart`, `updated_at:>'2024-01-01'`), and AND/OR/NOT. See the tool description for the full list of valid filter fields. Invalid fields are silently ignored and return all collections." } } }arguments 36 linessearch_products reads auth-required 13h ago
Search and browse products on a Shopify store. MUST be called whenever the user wants to see, find, or look at products in their store. Trigger phrases include: 'show me my products', 'what products do I have', 'list my products', 'browse my catalog', 'find a product', 'search for', or any reference to viewing multiple products. 'Show' and 'get' mean the same thing: always fetch live data from Shopify. Do NOT summarize from memory. Use this when the user wants to: - list or search products - look up a specific product by ID or handle - check product status or details - browse what's in their catalog Returns product data from the connected store via the Shopify Admin API. Results are capped at 50 per call. When `pageInfo.hasNextPage` is true, more matches exist than were returned. Tell the user you are showing the first N results and offer two paths: (a) load more via `after: pageInfo.endCursor`, or (b) refine the search with a stricter query. Only act on one of those paths when the user asks; do not auto-paginate. SEARCH SYNTAX: Free text matches across default fields (e.g. `shoes`, `"green hoodie"`). Field filters use `field:value`. Combine with `AND` / `OR` / `NOT`; parenthesize subqueries. Ranges use `:<`, `:<=`, `:>`, `:>=` on numeric/date fields. Example: `price:<=25 AND status:active`. IMPORTANT — invalid field names are silently ignored and return everything. Only use the fields listed below, as flat names. Do NOT invent dotted paths like `variants.price`, `product.tag`, or `variant.sku`. Supported filter fields: - Text / exact: `title`, `vendor`, `product_type`, `handle`, `sku`, `barcode`, `variant_title`, `tag`, `tag_not`, `status` (active|archived|draft) - Numeric (support ranges): `price` (matches products with ANY variant whose price satisfies the condition), `inventory_total`, `id`, `variant_id` - Date (support ranges): `created_at`, `updated_at`, `published_at` — use ISO 8601 in quotes, e.g. `created_at:>'2024-01-01'` - Boolean: `gift_card`, `bundles`, `is_price_reduced`, `out_of_stock_somewhere`, `tracks_inventory`, `has_only_default_variant` - ID: `collection_id`, `category_id` Price examples (cross-variant semantics): - `price:<=25` — products with at least one variant priced $25 or less - `price:>100 price:<=500` — products with at least one variant in $100–$500 - `price:25` — products with at least one variant priced exactly $25 SHOULD populate `search_summary` with a concise but descriptive plain-text heading in the user's language. Use a noun phrase that identifies the results as products instead of repeating only the search term—for example, "Your sneaker products", not "Your sneakers". The widget displays this text verbatim, so do not use Markdown. For a min/max of every variant or a product-wide price band, this tool cannot express it server-side; tell the user and suggest narrowing with `price:` plus another filter (e.g. `product_type:`, `vendor:`, `tag:`).
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "after": { "type": "string", "description": "Cursor for pagination. Use the endCursor from a previous response to fetch the next page." }, "first": { "type": "integer", "default": 10, "maximum": 50, "minimum": 1, "description": "Number of products to return (1-50, default 10)" }, "reverse": { "type": "boolean", "description": "Reverse the sort order (e.g. newest first with CREATED_AT + reverse)" }, "sort_key": { "enum": [ "TITLE", "PRODUCT_TYPE", "VENDOR", "INVENTORY_TOTAL", "UPDATED_AT", "CREATED_AT", "PUBLISHED_AT", "ID", "RELEVANCE" ], "type": "string", "description": "Sort key for results. Use RELEVANCE only when search_query is provided." }, "search_query": { "type": "string", "maxLength": 500, "description": "Search query to filter products. Uses Shopify search syntax: free text, field filters (`status:active`, `vendor:Nike`, `price:<=25`, `tag:sale`), and AND/OR/NOT. See the tool description for the full list of valid filter fields. Invalid fields are silently ignored and return all products." }, "search_summary": { "type": "string", "maxLength": 160, "minLength": 1, "description": "Concise but descriptive plain-text heading for these product results, written in the user's language. Identify the result type instead of repeating only the search term (for example, \"Your sneaker products\", not \"Your sneakers\"). The widget displays this text verbatim." } } }arguments 47 linessearch_docs_chunks unknown 25h ago
This tool will take in the user prompt, search shopify.dev, and return relevant documentation and code examples that will help answer the user's question.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "prompt" ], "properties": { "prompt": { "type": "string", "description": "The search query for Shopify documentation" }, "api_name": { "type": "string", "description": "The API name to filter search results by. Pass the same API name you used with learn_shopify_api (e.g., 'polaris-admin-extensions', 'pos-ui', 'admin'). This filters results to only return documentation for that specific API surface." }, "max_num_results": { "type": "number", "description": "Maximum number of results to return from the search. Do not pass this when calling the tool for the first time, only use this when you want to limit the number of results deal with small context window issues." } } }arguments 21 linesget-digital-product unknown 6h ago
Show the merchant a card for a digital product: its media image, title, price, status, and what the buyer receives. Call this after each step of the digital product flow — after the price is set, after the file is attached, after the media image is added, and after publishing — so the merchant sees the listing as it stands. Every field is read back from Shopify, so the card is current rather than a summary of what was asked for. This only reads. It changes nothing about the product.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "productId" ], "properties": { "productId": { "type": "string", "pattern": "^gid:\\/\\/shopify\\/Product\\/\\d+$", "description": "Product GID returned by create-digital-product." } } }arguments 14 linesvalidate_graphql_codeblocks unknown 6h ago
Compatibility no-op for clients that still call this tool. It always returns success and does not validate GraphQL syntax or schema. For Admin GraphQL, graphql_query and graphql_mutation validate operations against setup-mcp's pinned Admin schema immediately before execution.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "codeblocks" ], "properties": { "api": { "enum": [ "admin", "storefront-graphql", "partner", "customer", "payments-apps", "functions_cart_checkout_validation", "functions_cart_transform", "functions_delivery_customization", "functions_discount", "functions_discounts_allocator", "functions_fulfillment_constraints", "functions_local_pickup_delivery_option_generator", "functions_order_discounts", "functions_order_routing_location_rule", "functions_payment_customization", "functions_pickup_point_delivery_option_generator", "functions_product_discounts", "functions_shipping_discounts" ], "type": "string", "default": "admin", "description": "The GraphQL API to use. Valid options are:\n- 'admin': Write or explain Admin GraphQL queries and mutations for apps and integrations that extend the Shopify admin. Use this when the user wants to understand, design, or generate the operation itself. Prefer `admin-execution` instead when the user explicitly wants to run the operation against 'my store', 'this store', a store domain, or a warehouse/location, including simple store-result reads and multi-step store workflows that first look up IDs from handles, SKUs, or location names.\n- 'storefront-graphql': Use for custom storefronts requiring direct GraphQL queries/mutations for data fetching and cart operations. Choose this when you need full control over data fetching and rendering your own UI. NOT for Web Components - if the prompt mentions HTML tags like <shopify-store>, <shopify-cart>, use storefront-web-components instead.\n- 'partner': The Partner API lets you programmatically access data about your Partner Dashboard, including your apps, themes, and affiliate referrals.\n- 'customer': The Customer Account API allows customers to access their own data including orders, payment methods, and addresses.\n- 'payments-apps': The Payments Apps API enables payment providers to integrate their payment solutions with Shopify's checkout.\n- 'functions_cart_checkout_validation': GraphQL schema for Cart and Checkout Validation Function input queries\n- 'functions_cart_transform': GraphQL schema for Cart Transform Function input queries\n- 'functions_delivery_customization': GraphQL schema for Delivery Customization Function input queries\n- 'functions_discount': GraphQL schema for Discount Function input queries\n- 'functions_discounts_allocator': GraphQL schema for Discounts Allocator Function input queries\n- 'functions_fulfillment_constraints': GraphQL schema for Fulfillment Constraints Function input queries\n- 'functions_local_pickup_delivery_option_generator': GraphQL schema for Local Pickup Delivery Option Generator Function input queries\n- 'functions_order_discounts': GraphQL schema for Order Discounts Function input queries\n- 'functions_order_routing_location_rule': GraphQL schema for Order Routing Location Rule Function input queries\n- 'functions_payment_customization': GraphQL schema for Payment Customization Function input queries\n- 'functions_pickup_point_delivery_option_generator': GraphQL schema for Pickup Point Delivery Option Generator Function input queries\n- 'functions_product_discounts': GraphQL schema for Product Discounts Function input queries\n- 'functions_shipping_discounts': GraphQL schema for Shipping Discounts Function input queries\nDefault is 'admin'." }, "codeblocks": { "type": "array", "items": { "type": "object", "required": [ "content" ], "properties": { "content": { "type": "string", "description": "The GraphQL code block content which should contain raw GraphQL code (e.g., 'query { shop { name } }'), NOT markdown-formatted code blocks with backticks" }, "revision": { "type": "integer", "maximum": 9007199254740991, "description": "Monotonic revision number for the artifact. Start with 1 for new code, increment for each retry/iteration on the same artifactId. This helps track validation retries vs new validations.", "exclusiveMinimum": 0 }, "artifactId": { "type": "string", "description": "Stable id assigned to the generated code artifact. Use the same artifactId when retrying validation on modified code to track iterations." } } }, "description": "Array of GraphQL code blocks with content and optional artifact metadata" } } }arguments 60 linesget-product reads unknown 8h ago
Retrieve detailed information about a specific Shopify product by its GID, including title, status, vendor, variants, images, tags, and inventory. MUST be called whenever the user refers to a product they own or previously created — regardless of phrasing. Trigger phrases include: "my product", "that product", "the product", "show me my product", "get my product", "pull up the product", "open my product", or any reference to a previously created or known product. "Show" and "get" mean the same thing here: always fetch live data from Shopify. Do NOT rely on memory or prior responses — always call this tool for the source of truth.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The full product GID in the form gid://shopify/Product/<numeric_id> (e.g. gid://shopify/Product/123). Bare numeric IDs are NOT accepted — if you only have a product number, title, or SKU, call search-products first to look up the GID." } } }arguments 13 linesgraphql_query reads unknown 37m ago
Execute a read-only GraphQL query against the Shopify Admin API when no dedicated built-in tool covers the request. Raw schema introspection (__schema / __type) is not allowed through this tool. Use graphql_schema with operation 'query' to find an unknown query field or inspect its arguments and return type. Use operation 'schema' and type_name only for unfamiliar types needed by the query, including custom scalars whose value formats are unknown. Reuse schema details already discovered; skip built-in scalars (String, Int, Float, Boolean, ID). Never guess fields. After constructing the query, call this tool to execute it. The server validates Admin GraphQL against its pinned schema before sending the query to Admin. search_docs_chunks supplements schema discovery with examples but cannot replace it. Every connection returns at most 100 items per page, whether first or last is a literal or a variable and however deeply nested; a larger page is refused before it runs. For more items select pageInfo { hasNextPage endCursor }, then use the returned endCursor as the after variable. Present results clearly to the user rather than dumping raw JSON. For writes, discover the operation with graphql_schema using operation 'mutation', then use graphql_mutation.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "after": { "type": "string", "description": "Pagination cursor from a previous response's endCursor" }, "first": { "type": "integer", "default": 10, "maximum": 100, "minimum": 1, "description": "Number of items to return (1-100, default 10)" }, "query": { "type": "string", "minLength": 1, "description": "GraphQL query string" }, "variables": { "type": "object", "description": "GraphQL variables object", "propertyNames": { "type": "string" }, "additionalProperties": {} } } }arguments 33 linesget-inventory-levels reads unknown 8h ago
Retrieve inventory levels for all variants of a product across locations. Use this when the user asks about stock quantities, inventory availability, or wants to see how much inventory is at each location for a given product.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "productId" ], "properties": { "productId": { "type": "string", "description": "The product GID (e.g. gid://shopify/Product/123)" } } }arguments 13 linesgenerate-domain-names reads unknown 25h ago
Suggest available domain names for a Shopify store. Every domain returned has been checked against the domain registry and was available at the time of the call. WHEN TO USE: - The user wants a domain for a business or store name. - The user's preferred domain is taken and they want alternatives. - The user asks whether a domain idea is available. - The user wants to know what a domain costs. - The user wants to buy or register a particular domain. WHEN NOT TO USE: - The user wants to connect or troubleshoot a domain they already own — that is done in the Shopify admin, not here. - The user only wants store-name ideas and does not care whether a domain is available or what it costs. INPUT: a store name, a domain the user has in mind, or a short description of the business. All three work. If the user named a domain, the tool checks that exact domain, checks the same name at other common TLDs, and also returns 3 alternatives. An unusual TLD is fine — keep the one the user said. Pass the domain on its own as the query, or — when it sits inside a sentence — put it in exactDomain. If the user named no domain, put the words the domain should be built from in storeName: a name the user proposed ('volcanic balloon', 'Ember & Oak'), or the subject of what they described ('a domain about hippos, giraffes, and iguanas' → 'hippos giraffes iguanas'). Four words at most, lead-in and connecting words dropped, in the user's own words rather than converted to a domain yourself. The tool compresses them into a domain and checks that the same way; without storeName there is no availability check for a query like that, only suggestions. Only the exact domain checked can come back unavailable. Every other domain returned is available to buy, so do not describe any of them as taken, and do not say which TLDs were checked — an unlisted TLD may have been taken or may not have been quoted, and you cannot tell which. Every domain on offer carries a `signupUrl`, the one link that buys it, so present it rather than describing it. Where it leads depends on whether a Shopify store is connected to the call, not on whether the user owns one. With a store connected, it opens that domain's purchase page in that store's Shopify admin, so buying it attaches the domain to the store rather than starting a second one; the response says when this applies. Without one, it opens store signup with the domain already selected, even for a user who says they already have a store. Availability is a point-in-time check, not a hold. Tell the user to register a domain they want promptly, and never promise a domain is still available later in the conversation. Prices, where present, are the registry's quote for the first registration term in the stated currency. Renewal is priced separately and is often higher, so present a price as what registering costs today, not as an ongoing rate. A domain can come back without a price; say nothing about its cost rather than guessing, and in particular do not read a missing price as a domain that costs nothing. Every domain here has to be bought. Say a domain is "available" or "unavailable" — never that it is "free", which states a price rather than an availability and states it wrongly.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 255, "minLength": 1, "description": "REQUIRED — always send this field, in every call. A store name ('Ember & Oak'), a domain the user has in mind ('emberandoak.com'), or a short description of the business ('hand-poured soy candles for dark, woody scents') — max 255 characters. Use what the user actually said; do NOT invent a business description they have not given you. When the whole query is a domain ('fern.com') it is checked as one; when the domain sits inside a sentence ('is fern.com available?'), name it in exactDomain as well. storeName and exactDomain are extras that go ALONGSIDE this field, never instead of it: a call without query is rejected and the user gets nothing." }, "storeName": { "type": "string", "maxLength": 60, "minLength": 1, "description": "Optional. The words the domain should be built from — at most 4 words, max 60 characters. Set it whenever the user gave you something to build on, whether they named it or described it: 'what would be a good domain name for volcanic balloon' → 'volcanic balloon'; 'i want something like Ember & Oak' → 'Ember & Oak'; 'i want a domain about hippos, giraffes, and iguanas' → 'hippos giraffes iguanas'; 'hand-poured soy candles for dark, woody scents' → 'soy candles'. Drop the lead-in and the connecting words, and keep it to 4 words or fewer — a longer value is refused and the user loses the availability check. Omit it when the user already named a domain; exactDomain is where that belongs. Send it in addition to query, never instead of it. Do NOT invent words the user has not said, and do NOT convert it to a domain: this tool compresses these words itself and needs the user's own words to tell them what it derived from." }, "exactDomain": { "type": "string", "maxLength": 253, "minLength": 1, "description": "Optional. A full domain the USER named, TLD included, when the query is a sentence rather than the domain on its own: 'is fern.com available?' → 'fern.com'; 'can I get emberandoak.shop' → 'emberandoak.shop'. An unusual TLD is fine. This is the domain the tool reports a verdict on, so it must be one the user actually said — do NOT compose one from a name or a description, and do NOT guess a TLD they did not give. Use storeName for that instead; storeName and exactDomain are alternatives to each other, not a pair. Neither replaces query, which is always sent." } } }arguments 27 linesget-collection reads unknown 16h ago
Retrieve detailed information about a specific Shopify collection by its GID, including title, description, image, products, and rules (for smart collections). MUST be called whenever the user refers to a collection they own or previously created — regardless of phrasing. Trigger phrases include: "my collection", "that collection", "the collection", "show me my collection", "get my collection", or any reference to a previously created or known collection. "Show" and "get" mean the same thing here: always fetch live data from Shopify. Do NOT rely on memory or prior responses — always call this tool for the source of truth.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The collection GID (e.g. gid://shopify/Collection/123)" } } }arguments 13 linesgenerate-business-names reads unknown 37m ago
Generate business name ideas for someone starting a Shopify store. WHEN TO USE: - The user wants name ideas for a new business or store. - The user has described a business but has not named it yet. - The user has a name and wants alternatives in the same vein. WHEN NOT TO USE: - The user already knows the name they want and only needs to set it — that is done in the Shopify admin, not here. - The user wants a product name, a slogan, or a tagline rather than a business name. INPUT: a short description of the business in the user's own words — what they sell, who it is for, or the feeling they want ('hand-poured soy candles for dark, woody scents'). Max 255 characters. Pass what the user actually said; do NOT invent a business they have not described. Every name comes back with a `signupUrl`, the link that acts on it, so present it rather than describing it. Where it goes depends on the user: with no Shopify store connected it opens store signup with the name already filled in; with a store connected it opens the store name setting in that store's Shopify admin, where they save the new name themselves. Either way the tool only hands back a link — it creates and renames nothing. A store name is not exclusive, so the user can take any of these for their store. Nothing here is verified, though — no trademark search, no business registry, no check of whether someone else is already trading under the name — so tell them to check that before building a brand on it.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "description" ], "properties": { "description": { "type": "string", "maxLength": 255, "minLength": 1, "description": "REQUIRED — always send this field. A short description of the business in the user's own words: what they sell ('hand-poured soy candles'), who it is for ('running gear for trail runners'), or the feeling the name should have ('something calm and coastal'). Max 255 characters — a longer value is refused and the user gets nothing. Use what the user actually said rather than inventing a business for them, and send the description itself, not a name you have already thought of." } } }arguments 15 linesfind-mock-shop-catalogs reads unknown 37m ago
Find ready-made sample catalogs (from mock.shop) that fit the merchant's business, so they can pick one to seed their store with realistic products and collections instead of starting empty. WHEN TO USE: - The merchant has a new or empty store and wants sample products, a starter catalog, demo data, or "something to look at" before adding their own products. - The merchant describes what they sell (or plan to sell) and wants a store populated quickly. WHEN NOT TO USE: - The merchant wants one-off placeholder products rather than a whole catalog — use find-sample-product. - The merchant wants real products to source or resell — this returns sample data, not supplier inventory. - The merchant wants to browse products already in their store — use search-products. INPUT: a short description of the business or what it sells (e.g. "handmade soy candles", "supplies for a new puppy", "streetwear for teens"). Take it from what the merchant said. If they gave no hint at all, ask one question — what do they plan to sell? — then call. OUTPUT: up to `limit` catalogs (default 3), best match first. Each has a name, short description, categories, collection titles, product and collection counts, currency, and a `storefrontUrl` the merchant can open to browse it as a live storefront. Present them as a short list with the storefront links and ask the merchant which one they want. Pass the chosen catalog's `subdomain` to import-mock-shop-catalog to copy it into their store. An empty list means nothing matched well — suggest the merchant describe their business differently.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "limit": { "type": "integer", "maximum": 10, "minimum": 1, "description": "How many catalogs to return. Defaults to 3; leave unset unless the merchant asks for more options." }, "query": { "type": "string", "pattern": ".+", "maxLength": 500, "minLength": 1, "description": "What the merchant sells or plans to sell, in a few words (e.g. 'handmade soy candles', 'supplies for a new puppy'). Plain language; no need to singularize or reformat." } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idd12db4fd6a557470.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d12db4fd6a557470/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d12db4fd6a557470?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- hardware.shopify.com storefront-renderer