Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_delete_customer_meta

Destructive

Deletes WooCommerce customer metadata by key. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_customer_meta using local WordPress authentication; no WooCommerce REST API keys are required.

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_id": "<site_id>",
      "customerId": "<customerId>",
      "metaKey": "<metaKey>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_customer_meta"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true only after the user explicitly confirms deletion.
metaKeyYesThe metadata key to delete.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
customerIdYesThe WooCommerce customer ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds genuinely new context: a required user-confirmation gate and the fact that it uses local WordPress authentication with no WooCommerce REST keys needed. It does not say what happens if the key is absent, which would complete the picture.

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?

Three short sentences, purpose front-loaded, then the confirmation protocol, then auth context. No filler, though the confirmation instruction partially duplicates the confirm parameter description.

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, four-parameter mutation with no output schema, the description covers purpose, the confirmation prerequisite, and the auth model. Minor gaps remain around the result of deleting a non-existent key, but nothing critical to correct invocation is missing.

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 each parameter documented including the confirm gate and the site_id/list_sites dependency, so the schema carries the load. The description's confirmation sentence largely restates what the confirm parameter already says, adding no format or edge-case detail beyond it.

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 ('Deletes WooCommerce customer metadata by key'), which cleanly separates it from wc_delete_customer (whole customer) and wc_update_customer_meta (modification) in the sibling set. The 'by key' qualifier pins down the granularity of the operation.

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?

Provides a hard precondition ('Ask the user for confirmation before calling with confirm=true') but gives no guidance on when to prefer this over alternatives such as deleting the whole customer or updating metadata. Usage is implied by the verb rather than contrasted against siblings.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources