Skip to main content
Glama

shopify_update_customer

Destructive

Update a customer's name, email, phone, note, tax exemption, or tags in Shopify. Preview changes with dryRun mode before applying them.

Instructions

Update customer name, email, phone, note, tax exemption and tags (customerUpdate). dryRun:true (the default) returns the current customer and the change without applying it; dryRun:false applies it and returns before and after. Tags: addTags and removeTags change only the named tags; replaceTags replaces all tags. Email marketing consent is out of scope. Requires write_customers.

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": {
      "store": "<store>",
      "id": "<id>"
    },
    "name": "shopify_update_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
noteNo
emailNo
phoneNoE.164, for example +16135551111; null clears it.
storeYes
dryRunNoTrue (the default) returns a before/after preview without changing anything in Shopify. Pass false to apply the change; the tool then reads the result back.
addTagsNoTags to add (tagsAdd). Other tags are kept.
lastNameNo
firstNameNo
taxExemptNo
removeTagsNoTags to remove (tagsRemove). Other tags are kept.
replaceTagsNoReplaces all tags: every current tag not in this list is removed. Prefer addTags or removeTags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.2.0
    • addedInput schema / properties / firstName
      Added value: +{
      +  "maxLength": 255,
      +  "type": "string"
      +}
    • addedInput schema / properties / lastName
      Added value: +{
      +  "maxLength": 255,
      +  "type": "string"
      +}
    • addedInput schema / properties / phone
      Added value: +{
      +  "anyOf": [
      +    {
      +      "pattern": "^\\+[1-9][0-9]{6,14}$",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "E.164, for example +16135551111; null clears it."
      +}
    • addedInput schema / properties / taxExempt
      Added value: +{
      +  "type": "boolean"
      +}
  2. Addedv2.0.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag a destructive, open-world, non-idempotent write, but the description adds real context beyond them: the default is a non-mutating preview, the applied path reads the result back and returns before/after state, and replaceTags is called out as destroying any tag not listed. That is precisely the behavioral detail an agent needs before a destructive call.

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

Conciseness4/5

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

Purpose is front-loaded in the first clause, then behavior and tag semantics follow in descending order of importance. Semicolon-chained clauses make it dense and slightly hard to scan, but no sentence is filler.

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?

For a 12-parameter destructive mutation with no output schema, the description covers return behavior (preview vs before/after), tag replacement risk and auth requirements. Remaining gaps are minor, such as error behavior for a missing id or whether tag and field changes apply atomically.

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

Parameters4/5

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

Schema coverage is only 42%, so the description carries weight and does: it explains dryRun, and distinguishes addTags/removeTags (keep others) from replaceTags (destroys unlisted tags). It does not clarify that 'name' maps to the separate firstName/lastName properties, and required params id/store are left to the schema.

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

Purpose5/5

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

The description opens with a specific verb and resource ('Update customer') and enumerates the mutable fields (name, email, phone, note, tax exemption, tags), even naming the underlying mutation (customerUpdate). The 'customer' resource cleanly separates it from siblings like shopify_update_order and shopify_update_product without needing to name them.

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

Usage Guidelines5/5

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

It gives explicit guidance on the mode choice: dryRun:true previews, dryRun:false applies. It states a preference among tag parameters ('Prefer addTags or removeTags') and an explicit exclusion ('Email marketing consent is out of scope'), plus the required scope 'write_customers'.

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