Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_update_shipping_zone_locations

Destructive

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

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.
locationsYesShipping zone location objects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true. The description usefully adds the confirmation gate and the authentication model (local WordPress auth, no REST keys). It omits the most important behavior for this operation: whether the locations array replaces the entire existing set or merges with it.

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, then the safety instruction, then the auth note. No filler, though the mirrored-method sentence has limited value to an agent.

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 mutation with no output schema, the description covers the safety gate and auth model, which are the highest-risk unknowns. The replace-vs-merge ambiguity and lack of any indication of what is returned leave a meaningful gap.

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 zoneId, site_id and confirm are already documented. The description adds only the confirmation-gating semantics for confirm, which the schema also states. It adds nothing about the shape or required keys of the locations array objects.

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?

States a specific verb and resource: 'Updates locations assigned to a WooCommerce shipping zone.' This clearly distinguishes it from wc_get_shipping_zone_locations (read) and wc_update_shipping_zone (edits the zone itself, not its locations). It does not name those siblings explicitly, so differentiation relies on the noun phrase.

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 one clear procedural rule: ask the user for confirmation before calling with confirm=true. It gives no guidance on when to choose this over wc_update_shipping_zone or method-level siblings, and no precondition that a zone must already exist.

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