Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_update_shipping_zone

Destructive

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

Input Schema

NameRequiredDescriptionDefault
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.
zoneDataYesShipping zone fields to update.

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 risk profile is covered structurally. The description adds genuinely new context: a human-confirmation gate tied to the confirm flag, and the authentication model (local WordPress auth, no REST keys required), which explains why no credentials are needed.

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 safety requirement; nothing is padded. The trailing sentence about mirroring the woocommerce-mcp-server method is an implementation detail of marginal value but does signal behavioral parity.

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?

For a destructive mutation with a nested open-ended object parameter, the description does not say which zoneData fields are valid, whether the update is partial or full replacement, or what gets returned. Annotations and the schema cover safety and top-level params, but the most consequential ambiguity — the shape of zoneData — is left unaddressed.

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%, so this is the baseline case; all four parameters are documented in the schema. The description adds no meaning beyond it, particularly for zoneData, whose accepted fields remain unspecified even though additionalProperties=true makes it an open-ended object.

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?

The description opens with a specific verb and resource ('Updates a WooCommerce shipping zone'), which is unambiguous. It does not distinguish this tool from close siblings such as wc_update_shipping_zone_locations or wc_update_shipping_zone_method, so an agent must infer the boundary 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?

It gives one concrete usage rule: ask the user for confirmation and then pass confirm=true, which is actionable guidance. It offers no when-to-use or when-not-to-use guidance relative to the location/method update siblings, and no prerequisites beyond that.

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