Skip to main content
Glama
Jacques-Murray

WooCommerce MCP Server

Update WooCommerce Customer

woocommerce_update_customer
Idempotent

Update an existing WooCommerce customer's fields such as email, name, or addresses. Only supplied fields are changed, preserving other data.

Instructions

Update fields on an existing customer. Only supplied fields are changed.

Args:

  • customer_id (number, required)

  • Any subset of: email, first_name, last_name, billing, shipping

  • response_format ('markdown'|'json'): default 'markdown'

Returns: The updated customer object.

Error Handling:

  • Returns "Error: Resource not found (404)" if customer_id doesn't exist.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNo
billingNo
shippingNo
last_nameNo
first_nameNo
customer_idYesThe numeric WooCommerce customer ID to update
response_formatNoOutput format: 'markdown' for human-readable text or 'json' for machine-readable structured datamarkdown
Behavior4/5

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

The description adds context about partial updates and error handling (404 for missing customer), complementing annotations that indicate idempotency and non-destructiveness.

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 concise with four sentences covering purpose, args, returns, and error handling, front-loaded with the key point.

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?

The description adequately covers the main aspects for a simple CRUD update, but could improve by detailing nested parameters and validation behavior.

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?

Given low schema coverage (29%), the description lists the parameters and default response_format but lacks details on nested billing/shipping structures, providing partial compensation.

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 clearly states the tool updates an existing customer and that only supplied fields are changed, distinguishing it from create, delete, and get tools.

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 usage for partial updates but does not explicitly state when to use this tool over creating or deleting, or provide exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jacques-Murray/woocommerce-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server