wp-mcp-control-server

wp_delete_woocommerce_webhook

Delete a WooCommerce webhook by ID to remove it from your store. Confirmation required when safe mode is enabled.

Instructions

Delete a WooCommerce native webhook. confirm:true required when safe mode is on.

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": {
      "id": "<id>"
    },
    "name": "wp_delete_woocommerce_webhook"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	WooCommerce webhook ID
`confirm`	No	Required when safe mode is enabled

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.3.0Aug 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations present, the description carries the full burden of behavioral disclosure. It clearly indicates a destructive delete operation and adds the safe-mode confirmation requirement, which is valuable. However, it does not mention permanence, permissions, or what happens on success or failure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences with no filler. It states the purpose upfront and then adds the key operational caveat. Every word earns its place.

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 simple two-parameter delete operation, the description plus schema are largely sufficient. However, with no annotations, it could be more complete by noting that deletion is permanent or what happens in non-safe-mode when confirm is absent. The lack of an output schema does not hurt because the return value is not critical for this tool.

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 both parameters are already documented in the schema. The description adds no new semantic detail beyond restating confirm's condition, which the schema lists as 'required when safe mode is enabled.' The baseline of 3 applies.

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 uses a specific verb and resource, 'Delete a WooCommerce native webhook,' and the word 'native' helps distinguish it from sibling tools like wp_delete_custom_webhook and wp_delete_form_webhook. It is clear enough for an agent to identify the intended operation without opening the schema.

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?

Usage context is implied by the tool name and the 'native' descriptor, but the description does not explicitly state when to use this tool versus alternatives. The note about confirm being required in safe mode is a useful conditional, but there is no guidance for other scenarios.

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

Deploy Server