shopware-mcp

Get customer

customers_get

Read-onlyIdempotent

Retrieve a single customer by ID, customer number, or email with full addresses, group, and payment details. Returns one object for customer profile lookups.

Instructions

Get one customer by ID, customer number or email, including all addresses (with default billing/shipping flags), customer group, default and last used payment method. Returns one object.

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

Input Schema

Name	Required	Description
`email`	No
`fields`	No	Extra raw entity fields to add to each item, e.g. ['customFields', 'ean']. Dot-paths allowed.
`customerId`	No	Customer UUID
`customerNumber`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.11.1Nov 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds genuinely useful payload context — all addresses with default billing/shipping flags, customer group, and default/last-used payment method — plus the cardinality ("Returns one object"). It does not say what happens when no match is found, which is the remaining behavioral gap.

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?

Two sentences, no filler: the lookup keys and returned payload come first, with the return-shape statement placed last. Every clause carries information an agent needs.

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?

With no output schema, the description does its job of summarizing the returned object (addresses, group, payment methods) and confirming it is a single record. The main omission is not-found/error behavior and whether identifiers can be combined, which is minor for a simple read 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?

The description names three of the four inputs (customerId, customerNumber, email) as alternate lookup keys, adding a little meaning beyond the schema, though the schema already labels customerId as a UUID with a pattern. The fourth parameter, fields, is not mentioned in the description but is documented in the schema, and coverage overall is 50%.

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?

"Get one customer by ID, customer number or email" gives a specific verb, resource, and scope, and the singular "one customer" implicitly separates it from the sibling customers_search. It stops short of naming the sibling alternative explicitly, so it is clear but not fully differentiated.

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?

Usage is only implied: the phrasing "by ID, customer number or email" suggests at least one identifier must be supplied, which matters because the schema marks zero required parameters. There is no explicit when-to-use/when-not-to-use guidance or pointer to customers_search for list/query cases.

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