Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_woocommerce_webhooks

Retrieve configured WooCommerce native webhooks by product or order topic to review event triggers and verify integration setups.

Instructions

List WooCommerce native webhooks (product/order topics)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_woocommerce_webhooks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are present, so the description carries the disclosure burden. It communicates a read-only intent through 'List' and scopes the result to native webhooks with product/order topics, which prevents confusion with custom/form webhooks. However, it does not mention output shape, pagination, permissions, or any other behavior, leaving the agent to infer details beyond the minimal operation.

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 entire description is a single front-loaded sentence with no filler. Every element ('List', 'WooCommerce native webhooks', 'product/order topics') contributes to scope, so it earns a high conciseness score.

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 no-parameter read-only tool, the description is minimally sufficient: an agent knows exactly which resource is being listed and that it is the native, not custom or form, variant. Clear gaps remain, however, because there is no output schema and no description of return values or pagination, and the relationship to the many sibling webhook tools is only implicit through the word 'native'.

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

Parameters4/5

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

The input schema is empty and schema coverage is 100%, so there are no parameter semantics to document. With zero parameters, the description does not need to compensate for any parameter gaps; the baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('List') plus a resource ('WooCommerce native webhooks'), and the parenthetical '(product/order topics)' narrows the scope. The word 'native' distinguishes it from sibling custom-webhook and form-webhook listers, so an agent can tell this tool apart.

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?

The description identifies the target resource ('native webhooks') and thereby implies the WooCommerce-webhook context, but it never states when to prefer this tool over sibling listers like wp_list_custom_webhooks or wp_list_form_webhooks, nor does it specify exclusions. The 'native' qualifier gives some context, so the guidance is present but mostly implicit.

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

Deploy Server

Other Tools