Shopify Insights MCP

get_trending_products

Identify trending products by comparing sales between current and previous periods, revealing growth rates, rising stars, and declining products to guide inventory decisions.

Instructions

Identify trending products by comparing sales between the current period and the previous one. Shows growth rates, rising stars, and declining products.

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": "get_trending_products"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Number of products to show (default: 10)
`period`	No	Period to analyze (compares current vs previous)	week

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Aug 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains the comparison logic and the kinds of insights returned, which is useful. It does not mention the output structure, pagination, or any assumptions about how periods are calculated, but for a read-only analysis tool the core behavior is conveyed.

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 two sentences with no filler. It front-loads the core purpose and then lists the output categories, making it easy for an agent to scan and understand quickly.

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?

For a simple tool with two optional parameters and no output schema, the description covers the main behavior and output categories well. It could be more complete by describing the return format or clarifying period boundaries, but nothing essential is missing for selecting and invoking 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 100%, so the parameters are already well documented in the schema. The description adds no new parameter-level meaning beyond reinforcing that the period parameter compares current to previous, which the schema already states. Baseline 3 is appropriate.

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 identifies what the tool does: identify trending products by comparing current versus previous sales periods, and it names the outputs (growth rates, rising stars, declining products). It is distinct from siblings like get_sales_comparison and get_product_performance, though it does not explicitly name an alternative.

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?

The intended use case is implied: use it when you need to surface products that are trending or declining based on period-over-period sales. However, it offers no explicit guidance about when to choose this tool over related siblings such as get_product_performance or get_sales_comparison.

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

Deploy Server