Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Update webhook

tailscale_update_webhook
Idempotent

Update a webhook's endpoint URL or subscribed event types to modify where and which Tailscale events are sent.

Instructions

Update an existing webhook's endpoint URL and/or subscriptions.

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_update_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe webhook ID to update
endpointUrlNoNew HTTPS URL to send webhook events to
subscriptionsNoUpdated list of event types to subscribe to (at least one). 'categoryTailnetManagement' and 'categoryDeviceMisconfigurations' subscribe to a whole category, including events Tailscale adds to it later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / webhookId / minLength
      Added value: +1
  2. Changed2 schema fields changedv0.21.0
    • changedInput schema / properties / subscriptions / description
      Previous value: -"Updated list of event types to subscribe to (at least one)"New value: +"Updated list of event types to subscribe to (at least one). 'categoryTailnetManagement' and 'categoryDeviceMisconfigurations' subscribe to a whole category, including events Tailscale adds to it later."
    • changedInput schema / properties / subscriptions / items / enum
      Previous value: -[
      -  "exitNodeIPForwardingNotEnabled",
      -  "nodeApproved",
      -  "nodeCreated",
      -  "nodeDeleted",
      -  "nodeKeyExpired",
      -  "nodeKeyExpiringInOneDay",
      -  "nodeNeedsApproval",
      -  "nodeNeedsSignature",
      -  "nodeSigned",
      -  "policyUpdate",
      -  "subnetIPForwardingNotEnabled",
      -  "userApproved",
      -  "userCreated",
      -  "userDeleted",
      -  "userNeedsApproval",
      -  "userRestored",
      -  "userRoleUpdated",
      -  "userSuspended"
      -]New value: +[
      +  "categoryDeviceMisconfigurations",
      +  "categoryTailnetManagement",
      +  "exitNodeIPForwardingNotEnabled",
      +  "nodeApproved",
      +  "nodeCreated",
      +  "nodeDeleted",
      +  "nodeKeyExpired",
      +  "nodeKeyExpiringInOneDay",
      +  "nodeNeedsApproval",
      +  "nodeNeedsSignature",
      +  "nodeSigned",
      +  "policyUpdate",
      +  "subnetIPForwardingNotEnabled",
      +  "userApproved",
      +  "userCreated",
      +  "userDeleted",
      +  "userNeedsApproval",
      +  "userRestored",
      +  "userRoleUpdated",
      +  "userSuspended"
      +]
  3. Changed1 schema field changedv0.17.1
    • addedInput schema / properties / subscriptions / items / enum
      Added value: +[
      +  "exitNodeIPForwardingNotEnabled",
      +  "nodeApproved",
      +  "nodeCreated",
      +  "nodeDeleted",
      +  "nodeKeyExpired",
      +  "nodeKeyExpiringInOneDay",
      +  "nodeNeedsApproval",
      +  "nodeNeedsSignature",
      +  "nodeSigned",
      +  "policyUpdate",
      +  "subnetIPForwardingNotEnabled",
      +  "userApproved",
      +  "userCreated",
      +  "userDeleted",
      +  "userNeedsApproval",
      +  "userRestored",
      +  "userRoleUpdated",
      +  "userSuspended"
      +]
  4. First observedv0.13.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds only the 'and/or' optionality implication; it does not say whether omitted fields remain unchanged or whether subscriptions replace or merge with the current list, nor whether updating the endpoint affects the signing secret.

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?

A single front-loaded sentence with the resource and mutable fields first and zero filler. Nothing in it is redundant with itself or padded out.

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 three-parameter mutation with full schema coverage and annotations carrying the safety profile, the description is nearly sufficient. The remaining gap is partial-update and list-replacement semantics, which an agent would want to know before calling it.

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% and the schema itself explains the HTTPS requirement and the category-subscription semantics in detail. The description only restates the parameter names, adding no syntax, format, or defaulting information beyond what is already structured data.

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?

Uses a specific verb ('Update') on a specific resource ('an existing webhook') and names the mutable fields (endpoint URL, subscriptions), so it is clearly distinguishable from create_webhook or rotate_webhook_secret. It stops short of referencing any sibling by name, so a 4 rather than a 5.

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 or when-not-to-use guidance, and no mention of related siblings such as create_webhook (new webhook), delete_webhook, rotate_webhook_secret, or test_webhook. The only signal is the word 'existing', which implies an update path but requires the agent to infer the rest.

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