shopware-mcp

Get product

products_get

Read-onlyIdempotent

Retrieve one Shopware product by UUID with description, price, stock, tax, manufacturer, categories, media, properties, and all variants so agents can inspect complete product data.

Instructions

Get one product by ID with everything an agent usually needs: description, price, stock, tax, manufacturer, categories, properties, media and all variants with their options, stock and price. Use products_search or stock_get to find the ID first. Returns one object.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>"
    },
    "name": "products_get"
  }
}

Input Schema

Name	Required	Description	Default
`fields`	No	Extra raw entity fields to add to each item, e.g. ['customFields', 'ean']. Dot-paths allowed.
`productId`	Yes	Product UUID (32 hex chars)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely useful behavior context by describing the breadth of the returned aggregate (variants with options/stock/price) and stating "Returns one object" rather than a list. It stops short of noting error behavior for unknown IDs or any rate limits, which keeps it from a 5.

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?

Three short sentences, front-loaded with the capability statement, then the routing advice, then the return shape. The enumerated field list is dense but earns its place by telling the agent what it gets in one call.

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

Completeness5/5

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

There is no output schema, so the description must carry return-value meaning, and it does by enumerating the returned sections and clarifying that the result is a single object. Combined with fully documented parameters and safety annotations, nothing needed to call it correctly is missing.

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%, including a regex pattern for productId and a clear dot-path explanation for fields, so the schema carries the parameter burden and baseline 3 applies. The description adds only the phrase "by ID," which does not extend meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get one product by ID") and immediately enumerates the payload: description, price, stock, tax, manufacturer, categories, properties, media and variants. An agent can distinguish this single-entity fetch from products_search and stock_get without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Use products_search or stock_get to find the ID first," naming both alternatives and the missing prerequisite (the ID). This is a when-to-use-plus-prerequisite statement, leaving nothing to inference.

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