Skip to main content
Glama

woo_create_customer

Create a WooCommerce customer for a specified site using an email and optional billing, shipping, and account details. Use it to add new customers programmatically through WordPress MCP.

Instructions

Create a 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": {
      "site": "<site>",
      "email": "<email>"
    },
    "name": "woo_create_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
emailYesCustomer email
billingNoBilling address; only the given keys are set
passwordNoPassword (write-only, never returned; default: generated by WooCommerce)
shippingNoShipping address; only the given keys are set
usernameNoLogin name (default: generated by WooCommerce)
last_nameNoLast name
first_nameNoFirst name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv3.14.0
    • changedInput schema / properties / billing / additionalProperties
      Previous value: -{
      -  "type": "string"
      -}New value: +false
    • removedInput schema / properties / billing / default
      Removed value: -{}
    • addedInput schema / properties / billing / description
      Added value: +"Billing address; only the given keys are set"
    • addedInput schema / properties / billing / properties
      Added value: +{
      +  "address_1": {
      +    "type": "string"
      +  },
      +  "address_2": {
      +    "type": "string"
      +  },
      +  "city": {
      +    "type": "string"
      +  },
      +  "company": {
      +    "type": "string"
      +  },
      +  "country": {
      +    "description": "ISO 3166-1 alpha-2 country code, e.g. DE",
      +    "type": "string"
      +  },
      +  "email": {
      +    "type": "string"
      +  },
      +  "first_name": {
      +    "type": "string"
      +  },
      +  "last_name": {
      +    "type": "string"
      +  },
      +  "phone": {
      +    "type": "string"
      +  },
      +  "postcode": {
      +    "type": "string"
      +  },
      +  "state": {
      +    "description": "State/county code, e.g. BY",
      +    "type": "string"
      +  }
      +}
    • removedInput schema / properties / first_name / default
      Removed value: -""
    • addedInput schema / properties / first_name / description
      Added value: +"First name"
    • removedInput schema / properties / last_name / default
      Removed value: -""
    • addedInput schema / properties / last_name / description
      Added value: +"Last name"
    • removedInput schema / properties / password / default
      Removed value: -""
    • addedInput schema / properties / password / description
      Added value: +"Password (write-only, never returned; default: generated by WooCommerce)"
    • changedInput schema / properties / shipping / additionalProperties
      Previous value: -{
      -  "type": "string"
      -}New value: +false
    • removedInput schema / properties / shipping / default
      Removed value: -{}
    • addedInput schema / properties / shipping / description
      Added value: +"Shipping address; only the given keys are set"
    • addedInput schema / properties / shipping / properties
      Added value: +{
      +  "address_1": {
      +    "$ref": "#/properties/billing/properties/address_1"
      +  },
      +  "address_2": {
      +    "$ref": "#/properties/billing/properties/address_2"
      +  },
      +  "city": {
      +    "$ref": "#/properties/billing/properties/city"
      +  },
      +  "company": {
      +    "$ref": "#/properties/billing/properties/company"
      +  },
      +  "country": {
      +    "$ref": "#/properties/billing/properties/country"
      +  },
      +  "first_name": {
      +    "$ref": "#/properties/billing/properties/first_name"
      +  },
      +  "last_name": {
      +    "$ref": "#/properties/billing/properties/last_name"
      +  },
      +  "phone": {
      +    "$ref": "#/properties/billing/properties/phone"
      +  },
      +  "postcode": {
      +    "$ref": "#/properties/billing/properties/postcode"
      +  },
      +  "state": {
      +    "$ref": "#/properties/billing/properties/state"
      +  }
      +}
    • removedInput schema / properties / username / default
      Removed value: -""
    • addedInput schema / properties / username / description
      Added value: +"Login name (default: generated by WooCommerce)"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "email"
      -]New value: +[
      +  "site",
      +  "email"
      +]
  3. First observedv2.0.0

TDQS

C2.5/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 behavioral burden and conveys almost nothing: it does not say that this is a mutating write, whether duplicate emails are rejected, what permissions are needed, or what the response contains. Only the bare 'create' verb implies a write side effect.

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

Conciseness3/5

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

It is front-loaded and free of waste, but that is because it is almost empty rather than because it is tightly edited. Three words leave the structure with no room for the routing or behavioral detail an agent needs.

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

Completeness2/5

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

For an 8-parameter mutation tool with nested address objects and no annotations and no output schema, the description is far too thin. The rich schema compensates for parameter-level meaning, but the agent still gets no behavioral or return-value context.

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?

Schema description coverage is 100%, with nested billing/shipping objects and defaults for password and username all documented inline, so the baseline of 3 applies. The description adds no meaning beyond the schema, but it does not need to.

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

Purpose3/5

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

The description has a specific verb and resource (create a customer), which is clearer than a bare tautology, but it is only three words and does nothing to distinguish it from siblings such as woo_create_user or woo_update_customer. An agent knows roughly what it does but must lean on the name alone to differentiate.

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 when-to-use guidance, no mention of alternatives, and no stated prerequisites despite the schema requiring a site id. Nothing tells the agent whether to check for an existing customer first or when to prefer woo_update_customer.

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

Deploy Server

Other Tools