mcp-shopify

shopify_create_customer

Create a new customer in Shopify by providing email and optional details like name, phone, and tags for streamlined customer management.

Instructions

Create a new customer.

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": {
      "email": "<email>"
    },
    "name": "shopify_create_customer"
  }
}

Input Schema

Name	Required	Description	Default
`tags`	No
`email`	Yes
`phone`	No
`last_name`	No
`first_name`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

D1.5/5.0

Behavior1/5

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

No annotations are provided, so the description bears the full burden of behavioral disclosure. It says only that it creates a customer, with no mention of side effects, auth requirements, duplicate email handling, or response behavior. Even the basic mutation implication is already present in the tool name.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but this is under-specification, not conciseness. A single tautological sentence contains no structured information and does not earn its place beyond repeating the tool name.

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

Completeness1/5

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

For a tool with five parameters, one required, no parameter descriptions, and no output schema, this description is entirely inadequate. An agent cannot determine acceptable formats, required fields beyond email, tagging conventions, or what a successful creation returns.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not compensate by explaining any of the five parameters. Fields like tags, phone, and first_name are left completely undocumented, and the description adds no meaning to email's required role.

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

Purpose2/5

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

The description 'Create a new customer.' literally restates the tool name shopify_create_customer, adding no new information about the operation. It is a clear verb+resource but is a tautology rather than a purpose statement that distinguishes it from siblings like shopify_create_product or shopify_search_customers.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives such as shopify_create_product, shopify_update_product, or shopify_search_customers. The description omits any context about prerequisites, scenarios, or exclusions.

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

Deploy Server