Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete webhook

tailscale_delete_webhook
DestructiveIdempotent

Permanently deletes a Tailscale webhook by ID, removing its configuration and secret. Use it to stop webhook deliveries; deletion is irreversible and the secret cannot be recovered.

Instructions

Delete a webhook. This is irreversible -- the webhook secret cannot be recovered.

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": {
      "webhookId": "<webhookId>"
    },
    "name": "tailscale_delete_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe webhook ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / webhookId / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is partly covered structurally. The description adds genuinely new context beyond that: the deletion is irreversible and the webhook secret cannot be recovered, which tells the agent what is permanently lost. It stops short of mentioning permission requirements or whether the webhook must be disabled first, so it earns a 4 rather than a 5.

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 with zero waste: the action comes first, followed by the consequence that matters most. Nothing could be removed without losing information.

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 single-parameter delete with no output schema and annotations covering destructiveness and idempotency, the description supplies the one thing annotations cannot express — that the secret is unrecoverable. Mentioning prerequisites or a safer alternative (secret rotation) would make it fully complete.

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?

Only one parameter exists and schema description coverage is 100% ("The webhook ID to delete"), so the schema fully documents it. The description adds no further meaning about ID format or where to obtain the ID, which is acceptable at baseline but not additive.

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?

States a specific verb and resource ("Delete a webhook") with the scope fully unambiguous for this single-parameter tool. It does not explicitly differentiate from nearby write operations such as tailscale_update_webhook or tailscale_rotate_webhook_secret, but the verb+resource pairing is precise enough to identify the operation.

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?

There is no explicit when-to-use guidance and no mention of alternatives — notably tailscale_rotate_webhook_secret or tailscale_update_webhook, which an agent should consider before destroying a webhook. The irreversibility warning implicitly signals caution but does not route the agent anywhere.

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