get_productsLook up up to 50 products at once by SKU or by numeric id. Returns compact products (name, price ex/inc VAT, stock, link).
| Name | Required | Description | Default |
|---|---|---|---|
| ids | No | ||
| skus | No | ||
| locale | No | Storefront locale such as en-GB (default), en-US, de, fr-FR, es-ES, it-IT, nl-NL, pl. Controls product names, slugs and prices. |
| Name | Required | Description | Default |
|---|---|---|---|
| products | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "products": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "brand": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "brand_slug": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "categories": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "express_eligible": {
+ "description": "Website Express (same-working-day UK dispatch); only when the listing reports it.",
+ "type": "boolean"
+ },
+ "gtin": {
+ "type": "string"
+ },
+ "id": {
+ "type": "number"
+ },
+ "image": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "in_stock": {
+ "type": "boolean"
+ },
+ "mpn": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ },
+ "price": {
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "bulk_prices": {
+ "description": "Lower unit prices from min_quantity up.",
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "ex_vat": {
+ "type": "number"
+ },
+ "inc_vat": {
+ "type": "number"
+ },
+ "min_quantity": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "min_quantity",
+ "ex_vat",
+ "inc_vat"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "currency": {
+ "type": "string"
+ },
+ "ex_vat": {
+ "type": "number"
+ },
+ "inc_vat": {
+ "type": "number"
+ },
+ "on_sale": {
+ "type": "boolean"
+ },
+ "vat_rate": {
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "VAT rate in percent (20 = 20%). null when unknown: ex_vat then equals inc_vat."
+ },
+ "was_ex_vat": {
+ "type": "number"
+ },
+ "was_inc_vat": {
+ "description": "Price before the sale; only when on_sale.",
+ "type": "number"
+ }
+ },
+ "required": [
+ "currency",
+ "ex_vat",
+ "inc_vat",
+ "on_sale",
+ "vat_rate"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "null when the product has no online price."
+ },
+ "sku": {
+ "type": "string"
+ },
+ "slug": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "stock_level": {
+ "type": "number"
+ },
+ "summary": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "url": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "required": [
+ "id",
+ "sku",
+ "name",
+ "slug",
+ "url",
+ "brand",
+ "brand_slug",
+ "categories",
+ "price",
+ "in_stock",
+ "stock_level",
+ "image",
+ "summary"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "products"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and destructiveHint, covering the safety profile. The description adds useful behavioral context by noting that the result is a compact projection (name, price ex/inc VAT, stock, link) rather than full product records. No contradiction with annotations.
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?
Two sentences with no wasted words. The action, resource, limit, and selection keys are front-loaded, and the return-shape note is compact.
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 batch read tool with a rich output schema and read-only annotations, the description is largely sufficient: it explains what to pass and what kind of data comes back. It could be improved by explicitly routing single-product or search scenarios to siblings, but that is more of a usage-guideline refinement than a completeness gap.
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 only 33%, so the description must compensate. It maps 'SKU' to the skus parameter and 'numeric id' to the ids parameter, adding minimal domain meaning. However, it does not clarify whether ids and skus can be mixed, whether at least one is required, or how locale affects output beyond what the schema already states.
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?
Description states a specific verb ('Look up'), resource ('products'), and the exact selection mechanism ('by SKU or by numeric id') with a batch limit of 50. The phrase 'Returns compact products' helps distinguish it from single-product get_product or broad search_products.
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 description clearly implies when to use it: when you already have SKUs or numeric IDs and need several products at once. It does not explicitly name alternatives or exclusion conditions, such as using get_product for a single product or search_products for fuzzy lookup, but the context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.