shopify_get_customerRetrieve a Shopify customer's full profile including addresses, tags, last five orders, and lifetime spend to support order and account management.
Full customer profile: all addresses, tags, order history (last 5 orders), and lifetime spend.
| Name | Required | Description | Default |
|---|---|---|---|
| customerId | Yes | Customer GID e.g. gid://shopify/Customer/1234567890 |
Changes observed during successful MCP inspections.
v4.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds return-scope context beyond the annotations, notably that order history is limited to the last 5 orders and includes lifetime spend, which helps an agent anticipate payload shape.
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?
One compact sentence with the content list front-loaded and zero filler. Every clause earns its place by describing the returned profile.
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?
With no output schema, the description takes on the job of conveying return content and does so reasonably (addresses, tags, orders, spend). It lacks error/not-found behavior and pagination notes, but for a single-record read with full annotation coverage it is largely complete.
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?
There is a single customerId parameter with 100% schema description coverage including the GID format example. The description adds no additional parameter meaning, so the schema carries the burden and baseline 3 applies.
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?
The description states a specific retrieval action ('Full customer profile') for the customer resource and enumerates the returned content (addresses, tags, last 5 orders, lifetime spend). This clearly distinguishes it from siblings like shopify_search_customers (listing/lookup) and shopify_get_customer_events (events).
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?
Usage is only implied by the ID-based title and the 'Full customer profile' phrasing; there is no explicit when-to-use guidance and no mention of alternatives such as shopify_search_customers for finding a customer ID first. Adequate minimum viable context but no routing help.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.