Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_delete_shipping_zone

Destructive

Deletes a WooCommerce shipping zone. Ask the user for confirmation before calling with confirm=true. Mirrors woocommerce-mcp-server method delete_shipping_zone 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>",
      "zoneId": "<zoneId>",
      "confirm": "<confirm>"
    },
    "name": "wc_delete_shipping_zone"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoIf true, permanently delete where WooCommerce supports forced deletion.
zoneIdYesThe shipping zone ID.
confirmYesMust be true only after the user explicitly confirms this WooCommerce mutation.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 real value beyond that: an explicit human-confirmation gate and the authentication model (local WordPress auth, no REST API keys), which an agent needs before attempting the call. It stops short of describing side effects such as what happens to a zone's methods/locations.

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, front-loaded with the action and then the confirmation rule. The final sentence about mirroring woocommerce-mcp-server and REST API keys is the weakest, though it does convey deployment/auth context an agent may find useful.

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

Completeness3/5

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

Covers the confirmation workflow and auth model, which are the key gaps for a destructive tool with no output schema. However, for an irreversible delete it should say whether the zone and its attached methods/locations are removed together, whether the default zone is protected, and what a successful response looks like.

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 coverage is 100%, so all four parameters already carry inline descriptions including the confirm contract and the site_id/list_sites instruction. The description mainly restates the confirm requirement and adds nothing about force semantics or default-zone edge cases; baseline 3 applies when the schema does the heavy lifting.

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

Purpose4/5

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

Names a specific verb and resource: "Deletes a WooCommerce shipping zone." The resource is distinct from the sibling wc_delete_shipping_zone_method by naming 'zone' explicitly, but the description never calls out that distinction, so an agent must infer it from names alone.

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?

Gives a procedural precondition (ask the user for confirmation, then pass confirm=true) but no guidance on when to choose this over wc_update_shipping_zone or wc_delete_shipping_zone_method, and no mention of when force should or should not be set. Usage is implied rather than explained.

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