Skip to main content
Glama
Sign In
wuapi MCP server

wuapi MCP server

Official
by wuapidev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete an incoming webhook

delete_incoming_webhook
DestructiveIdempotent

Delete an incoming webhook. Its URL stops working at once, for whatever still calls it.

Instructions

Delete an incoming webhook. Its URL stops working at once, for whatever still calls it.

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": {
      "incomingWebhookId": "<incomingWebhookId>",
      "confirm": "<confirm>"
    },
    "name": "delete_incoming_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true. Whatever calls the URL stops sending. Only set it after the user asked for this or agreed to it.
incomingWebhookIdYesThe incoming webhook id, from list_incoming_webhooks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.13.1

TDQS

A3.8/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 safety profile is covered. The description adds real context beyond them: the URL stops working immediately ('at once'), clarifying that the effect is instantaneous and affects any caller still using it. It does not address auth/ownership requirements, but that is carried by the schema's confirm field.

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 short sentences, zero waste, with the core action and its immediate consequence front-loaded. Nothing redundant with the title or schema.

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 destructive, no-output-schema tool whose annotations already cover safety and idempotency, the description plus schema give an agent what it needs to call correctly. A minor gap is the absence of explicit guidance on when deletion is preferable to updating/disabling the webhook.

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%; the confirm field already documents the mandatory-true confirmation and the incomingWebhookId points to list_incoming_webhooks. The description adds no parameter-level detail beyond what the schema provides, so the baseline 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 states a specific verb and resource ('Delete an incoming webhook'), and the resource qualifier 'incoming' distinguishes it from the sibling delete_webhook (outgoing webhook). It stops short of naming any alternative explicitly, so it is clear but not sibling-routing.

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 phrase 'for whatever still calls it' implies the intent (stop URL traffic), but there is no explicit when-to-use guidance or comparison against update_incoming_webhook (which could disable/rotate without deleting) or list_incoming_webhooks. Usage is implied rather than stated.

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