Skip to main content
Glama
Jacques-Murray

WooCommerce MCP Server

List WooCommerce Customers

woocommerce_list_customers
Read-onlyIdempotent

Search and filter registered customers by email, name, or role, returning ID, email, order count, and total spent.

Instructions

Search and list registered customers (does not include guest checkout customers, who aren't stored as customer records).

Args:

  • search (string, optional): match against name/email/username

  • email (string, optional): exact match

  • role (string, optional): WordPress role filter

  • orderby / order: sorting (default name/asc)

  • page / per_page: pagination (default page=1, per_page=20, max 100)

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

Returns: paginated list of customers with id, email, name, order count, and total spent.

Examples:

  • Use when: "find the customer with email jane@example.com" -> email="jane@example.com"

  • Don't use when: looking up who placed a guest order (check the order's billing details instead)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to retrieve, 1-based (default: 1)
roleNoFilter by WordPress user role, e.g. 'customer', 'subscriber'
emailNoFilter by exact email address
orderNoSort direction (default: asc)asc
searchNoSearch term to match against name/email/username
orderbyNoSort field (default: name)name
per_pageNoNumber of results per page, 1-100 (default: 20)
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?

Annotations already indicate read-only, idempotent, non-destructive. Description adds important nuance that guest checkout customers are excluded, and details pagination/sorting defaults, enhancing understanding beyond annotations.

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?

Well-structured with Args, Returns, Examples sections. Every sentence adds value; no redundancy or fluff.

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

Completeness5/5

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

Despite no output schema, description details return fields (id, email, name, order count, total spent) and covers all parameters with pagination limits, fully informing usage.

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 description coverage is 100%, but the description adds usage examples (e.g., email='jane@example.com') and organizes parameters with clear explanations, providing extra context.

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 'Search and list registered customers' with a specific exclusion of guest checkout customers, distinguishing it from other tools like 'woocommerce_get_customer'.

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?

Provides explicit examples of when to use (e.g., find customer by email) and when not to use (guest order lookup with pointer to billing details), offering clear alternative guidance.

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