Fetch normalized product details from any Shopify storefront using a product handle and store URL. Retrieves credential-free JSON via the public .js endpoint.
Get Shopify product. Returns normalized product detail from Shopify's credential-free product handle .js endpoint.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Shopify storefront URL | |
| handle | Yes | Product handle |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the transparency burden. It discloses that the endpoint is credential-free, which is a useful behavioral trait. However, it does not mention read-only nature, rate limits, or error handling for invalid handles.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise with two sentences, no wasted words, and front-loaded with the verb and resource. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has only 2 parameters, no output schema, and no annotations, the description is minimally adequate. It states what is returned (normalized product detail) but lacks specifics about the output format or any constraints. Could be improved with example or field hints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with descriptions for both parameters ('handle' and 'url'). The description reinforces that the handle is the product identifier but adds no additional meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Get' and resource 'Shopify product', and distinguishes itself by mentioning the specific endpoint ('credential-free product handle .js endpoint'), which differentiates it from sibling tools like shopify_products or shopify_product_recommendations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternatives. The description implies it is for retrieving a single product detail from Shopify, but does not mention exclusions or comparison with sibling tools like shop_app_product or shopify_products.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.