AIVA MCP Server

shopify_get_product

Retrieve detailed product information from Shopify stores using product ID or handle. This tool enables access to product data for managing inventory, analytics, and customer intelligence within the AIVA MCP Server environment.

Instructions

Get product details by ID or handle.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "shopify_get_product"
  }
}

Input Schema

Name	Required	Description	Default
`productId`	No	Product ID
`handle`	No	Product handle (alternative to ID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jan 24, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, authentication requirements, rate limits, error handling, or what 'details' include. The phrase 'Get product details' implies safe retrieval but offers no concrete behavioral context.

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?

Extremely concise with a single, front-loaded sentence that directly states the tool's function. Every word earns its place with no redundancy or fluff, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple retrieval tool with 2 parameters and no output schema, the description is minimally adequate. It covers the core purpose but lacks context on authentication, error cases, return format, or sibling differentiation. Without annotations or output schema, more behavioral transparency would improve completeness.

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 description coverage is 100%, so parameters are documented in the schema. The description adds minimal value by noting these are alternatives ('ID or handle'), but doesn't explain format differences, precedence if both provided, or handle syntax. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the verb ('Get') and resource ('product details'), specifying retrieval by 'ID or handle'. It distinguishes from sibling 'shopify_get_products' (plural) by focusing on single product lookup, but doesn't explicitly contrast with other Shopify tools like 'shopify_get_customer' or 'shopify_get_orders'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention when to choose ID vs handle, prerequisites like authentication, or comparison with sibling tools like 'shopify_get_products' for bulk retrieval. Usage is implied but not explicitly defined.

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

Deploy Server