mcp-shopify

shopify_get_customer

Fetch a customer record by ID to access contact details, account status, and order history. Resolves customer information quickly for support or admin tasks.

Instructions

Get a customer by ID.

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": {
      "customerId": "<customerId>"
    },
    "name": "shopify_get_customer"
  }
}

Input Schema

Name	Required	Description	Default
`customerId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not mention error behavior, authentication requirements, rate limits, or whether the returned object includes addresses, tags, or other fields. For a tool with no annotations, this is a meaningful 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?

The description is a single, direct sentence with no filler. It fully answers the basic 'what does this tool do' question in minimal words, which is ideal for an agent parsing a tool list.

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

Completeness3/5

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

Given the low complexity of a single-parameter get-by-ID operation, the description is minimally adequate for making the call. However, with no output schema and no annotations, returning behavior and expected payload shape are left unspecified, so the description is not as complete as it could be.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the sole parameter, but it only restates that the customer is fetched by ID. The schema already documents customerId as a positive integer; the description does not add meaningful semantics such as where the ID comes from, whether it supports external IDs, or how invalid IDs are handled.

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 names a specific verb and resource, 'Get a customer by ID,' which clearly conveys a single-customer retrieval operation. The 'by ID' qualifier distinguishes it from list/search customer tools, though it does not explicitly reference them or describe what fields are returned.

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 description implies this tool is used when a customer's ID is known, but it gives no explicit guidance on when to choose this over alternatives like shopify_search_customers or shopify_list_customers. There is no mention of prerequisites or exclusions, leaving the usage context mostly inferential.

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

Deploy Server