AIVA MCP Server

shopify_get_products

Search and list products from a connected Shopify store using filters like query, collection, or product type to retrieve specific inventory data.

Instructions

Search and list products from the connected Shopify store.

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_products"
  }
}

Input Schema

Name	Required	Description
`query`	No	Search query
`collection`	No	Filter by collection handle
`productType`	No	Filter by product type
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jan 24, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'Search and list' but doesn't clarify if this is a read-only operation, what permissions are needed, whether it supports pagination, rate limits, or error handling. For a tool with 4 parameters and no annotation coverage, this leaves significant behavioral gaps.

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?

The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence earns its place by conveying essential information about the tool's function and scope.

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

Completeness2/5

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

Given the tool's complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks details on behavioral traits, usage context, output format, and doesn't fully address the gaps in parameter documentation, making it insufficient for an agent to confidently invoke the tool.

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 75%, with three parameters having descriptions and one ('limit') having only a default. The description adds no additional parameter semantics beyond implying search and filtering capabilities through 'Search and list' and 'from the connected Shopify store', which doesn't compensate for the partial schema coverage. Baseline 3 is appropriate as the schema does most of the work.

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 action ('Search and list') and resource ('products from the connected Shopify store'), providing a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'shopify_get_product' (singular), which might retrieve a single product, leaving some ambiguity about sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'shopify_get_product' or 'aiva_search_customers', nor does it specify prerequisites, contexts, or exclusions for usage, leaving the agent without clear selection criteria.

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

Deploy Server