WooCommerce MCP Server

create_webhook

Set up automated notifications for WooCommerce events like orders, products, customers, and coupons by creating webhooks that send data to specified URLs.

Instructions

Create a webhook. Topics: order.created, order.updated, order.deleted, product.created, product.updated, product.deleted, customer.created, customer.updated, coupon.created, coupon.updated, etc.

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": {
      "name": "<name>",
      "topic": "<topic>",
      "delivery_url": "<delivery_url>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Default
`name`	Yes
`topic`	Yes
`delivery_url`	Yes
`secret`	No
`status`	No	active

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 21, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states what the tool does (create) and lists topics, but doesn't mention permissions needed, rate limits, whether creation is idempotent, what happens on duplicate webhooks, or what the response contains. For a mutation tool with zero annotation coverage, this is insufficient.

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?

The description is brief and front-loaded with the core purpose. The topic list is efficiently presented as examples rather than exhaustive enumeration. However, the 'etc.' at the end suggests incomplete information which slightly reduces clarity.

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?

Given this is a mutation tool with 5 parameters, 0% schema description coverage, no annotations, but with an output schema, the description is moderately complete. The output schema reduces the need to describe return values, but the description lacks crucial context about permissions, side effects, and parameter meanings that would be needed for safe usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for undocumented parameters. The description only mentions 'Topics' which maps to the 'topic' parameter, leaving 4 other parameters (name, delivery_url, secret, status) completely unexplained. The topic examples are helpful but don't cover the full parameter set.

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 clearly states the verb 'Create' and resource 'webhook', making the purpose immediately understandable. It distinguishes from siblings like 'delete_webhook' and 'list_webhooks' by specifying creation. However, it doesn't explicitly differentiate from other 'create_' tools beyond listing topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when webhooks are appropriate, or how this differs from other notification methods. The topic list implies scope but doesn't provide decision criteria.

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