Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WooCommerce: Delete customer

woocommerce_delete_customer
Destructive

Permanently delete a WooCommerce customer while preserving their past orders and optionally reassigning their posts to another user ID.

Instructions

[UNIFIED] Permanently delete a WooCommerce customer (customers cannot be trashed). Their past orders are kept. Optionally reassign the user's posts to another user ID.

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>",
      "customer_id": "<customer_id>"
    },
    "name": "woocommerce_delete_customer"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
reassignNo
customer_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real consequence detail beyond them: deletion is permanent with no trash fallback, past orders survive, and posts can be reassigned. It stops short of permission requirements, confirmation needs, or what the call returns.

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?

Three short sentences, each earning its place, with the destructive verb and irreversibility front-loaded before the side-effect details. The '[UNIFIED]' tag is the only disposable token.

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 destructive three-parameter mutation with no output schema, the description covers the things an agent most needs: irreversibility, order retention, and post-reassignment. Auth requirements and the response shape are absent, but the critical cautionary context is present.

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?

With 0% schema description coverage, the description carries the full burden, and it explains only the optional 'reassign' parameter (target user ID for the customer's posts). 'site' and 'customer_id' are left entirely to the schema's types, so the compensation is partial.

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?

States a specific verb and resource ('Permanently delete a WooCommerce customer') and immediately scopes it against an alternative disposition ('customers cannot be trashed'), so an agent knows this is a hard delete, not a soft one. The resource name alone separates it from the delete_coupon/delete_order/delete_product siblings.

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 'customers cannot be trashed' clause implicitly tells the agent this is the only removal path, and 'permanently' flags the stakes. However, there is no explicit when-to-use / when-not-to-use guidance or routing to alternatives such as deactivating or updating a customer instead.

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