Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_update_shipping_zone_method

Destructive

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

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.
instanceIdYesThe shipping method instance ID.
methodDataYesShipping method fields to update.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the risk profile is known. The description adds two genuinely non-annotated facts: the user-confirmation workflow and that local WordPress auth is used with no WooCommerce REST API keys needed. It does not say what is overwritten in methodData, whether omitted fields are preserved, or how failures behave.

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 immediately followed by the confirmation prerequisite. The closing sentence about mirroring the upstream method name and auth mode is partly filler for tool selection, but it does carry useful auth context, so only minor trimming is warranted.

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?

A destructive mutation with no output schema needs the description to cover prerequisites, risk, and payload expectations; it covers the confirmation prerequisite and auth, but leaves the updatable methodData fields and post-update outcome unspecified. Adequate to call safely, not fully complete.

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%, including the confirm and site_id semantics, so the schema carries the explanatory load and baseline 3 applies. The description adds nothing about the free-form nested methodData object (empty properties, additionalProperties=true), which is the one parameter where an agent would benefit from description-level hints.

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 a shipping method in a WooCommerce shipping zone'), which distinguishes it from create/delete siblings by name pattern. It stops short of explicitly contrasting with the adjacent wc_update_shipping_zone or wc_update_shipping_zone_locations, so an agent must infer the boundary from the resource noun 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?

Provides one concrete procedural rule: ask the user for confirmation, then pass confirm=true. It gives no guidance on when to prefer this tool over updating a whole zone, zone locations, or deleting/recreating a method, so the 'which sibling' decision is only implied by the resource name.

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