Skip to main content
Glama
Sign In
wuapi MCP server

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a webhook endpoint

delete_webhook
DestructiveIdempotent

Delete a webhook endpoint to stop all incoming events and retries instantly. Confirm with 'true' to permanently deactivate the endpoint.

Instructions

Delete a webhook endpoint. Its events stop at once, including deliveries still retrying.

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": {
      "webhookEndpointId": "<webhookEndpointId>",
      "confirm": "<confirm>"
    },
    "name": "delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. The endpoint stops receiving events. Only set it after the user asked for this or agreed to it.
webhookEndpointIdYesThe webhook endpoint id, from list_webhooks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description does not need to restate those. It adds valuable context by noting that events stop at once, including deliveries still retrying, which is a behavioral nuance beyond what annotations provide.

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?

Two sentences with no fluff. The primary action and its immediate consequence are front-loaded, making it easy for an agent to grasp the tool's function quickly.

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 simple delete operation with destructive and idempotent annotations, the description covers the essential behavioral impact. No output schema is present, but the response is likely minimal. The only minor gap is the lack of mention of prerequisites or error handling, but that is not critical for this tool type.

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% with both parameters well-documented (webhookEndpointId sourced from list_webhooks, confirm requiring explicit user consent). The description itself adds no parameter information, so it relies on the schema, which is fully adequate. Baseline 3 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 clearly states the action ('Delete a webhook endpoint') with a specific resource and adds the immediate effect of stopping events, including retrying deliveries. This distinguishes it from sibling tools like create_webhook or update_webhook without ambiguity.

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 explains what the tool does but does not explicitly state when to use it over alternatives like update_webhook or list_webhooks. The context of sibling tools makes it obvious for a delete action, but there is no explicit guidance or exclusion, such as 'use only when the endpoint is no longer needed'.

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