Skip to main content
Glama
Sign In

Shopify

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Shopify Get Product

shopify_get_product
Read-onlyIdempotent

Fetch a single Shopify product by numeric ID, returning its title, description, variants, pricing, inventory, and images via the Admin API.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": 632910392,
      "_shop": "mystore.myshopify.com",
      "_apiKey": "your-shopify-api-key"
    },
    "name": "shopify_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesProduct ID
_shopYesShop domain (e.g., mystore.myshopify.com)
_apiKeyYesShopify Admin API access token

Output Schema

NameRequiredDescriptionDefault
productNoProduct details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "product": {
+      "description": "Product details",
+      "properties": {
+        "body_html": {
+          "description": "Product description HTML",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "created_at": {
+          "description": "Creation timestamp",
+          "type": "string"
+        },
+        "handle": {
+          "description": "Product handle/slug",
+          "type": "string"
+        },
+        "id": {
+          "description": "Product ID",
+          "type": "number"
+        },
+        "product_type": {
+          "description": "Product type",
+          "type": "string"
+        },
+        "published_at": {
+          "description": "Publication timestamp",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "status": {
+          "description": "Product status",
+          "type": "string"
+        },
+        "tags": {
+          "description": "Comma-separated tags",
+          "type": "string"
+        },
+        "title": {
+          "description": "Product title",
+          "type": "string"
+        },
+        "updated_at": {
+          "description": "Last update timestamp",
+          "type": "string"
+        },
+        "variants": {
+          "description": "Product variants",
+          "type": "array"
+        },
+        "vendor": {
+          "description": "Product vendor",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-shopify-api-key",
+    "_shop": "mystore.myshopify.com",
+    "id": 632910392
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds that it uses the Admin API and lists returned fields, but does not disclose additional behavioral traits (e.g., rate limits, authentication details). The description does not contradict annotations.

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?

Single sentence, front-loaded with action and expected results. No extraneous words, highly efficient.

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?

Has output schema (referenced in context). Description covers the main returned fields. For a simple read tool with good annotations and full schema coverage, the description is adequately complete, though it could mention pagination or edge cases.

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% with clear parameter descriptions. The description mentions 'numeric ID' but adds minimal value beyond the schema (e.g., no further guidance on formatting or constraints). Baseline 3 applies due to high schema coverage.

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?

The description clearly states the tool fetches a single Shopify product by numeric ID, specifying the returned fields (title, description, variants, pricing, inventory, images). It distinguishes from siblings like shopify_list_products (multiple products) and shopify_get_order (different resource).

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?

No explicit when/when-not/alternatives are given. The description implies usage for fetching a single product, and sibling tool names (e.g., shopify_list_products) provide context, but no direct guidance on when to use this vs. alternatives.

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

All Shopify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources