Retrieve a single Shopify product by its ID to access details such as title, price, and inventory. Use this tool when you need specific product information from your store.
Get a product by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| productId | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description must carry the behavioral disclosure burden. The word 'Get' communicates a read-only retrieval, and there are no obvious destructive side effects, but the description does not mention error behavior, authorization needs, or what is returned.
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?
One short sentence with no filler. The key information is front-loaded and every word contributes to the meaning.
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?
For a simple single-parameter retrieval tool, this is minimally adequate, but it leaves gaps: it does not clarify the identifier semantics, what product data is returned, or how to handle not-found cases. It is not as rich as it could be for a Shopify-specific API call.
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 description coverage is 0%, and the description adds no real meaning beyond the schema's existing 'productId' property name. It does not clarify that this is the Shopify numeric product ID, not an SKU, handle, or external identifier, so the lone required parameter is not fully explained.
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 uses a specific verb ('Get') and resource ('product') and identifies the uniqueness criterion ('by ID'). This clearly separates it from siblings like shopify_list_products, shopify_create_product, and shopify_update_product.
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?
The phrase 'by ID' implies this tool should be used when the agent has a specific product ID, but it does not explicitly say when not to use it or name alternatives. No guidance is given about using shopify_list_products for browsing products or how to obtain a product ID.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.