Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update webhook

tailscale_update_webhook
Idempotent

Update an existing webhook's endpoint URL and event subscriptions to direct notifications to the correct destination.

Instructions

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

Input Schema

TableJSON 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. 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"
+]
  2. 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"
+]
  3. First observedv0.13.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already convey that this is not read-only, is idempotent, and is not destructive, so the description does not need to restate those facts. It adds only a weak hint of partial update via 'and/or' and does not explain whether omitted fields are preserved or what the response looks like, though the annotations lower the burden here.

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 description is a single sentence, front-loaded with the action and resource, and contains no filler or redundant information. Every word contributes to understanding what the tool does.

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 simple three-parameter update tool with annotations covering safety, the definition is mostly adequate. However, it does not clarify partial-update behavior when only webhookId is provided, and with no output schema the agent cannot anticipate the return shape.

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 already documents webhookId, endpointUrl, and subscriptions thoroughly. The description's mention of 'endpoint URL and/or subscriptions' adds no meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the action ('Update'), the resource ('existing webhook'), and the exact fields in scope ('endpoint URL and/or subscriptions'). It is distinct from create/delete by saying 'existing', though it does not explicitly name sibling tools to differentiate from.

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 verb and resource imply this tool is for modifying an existing webhook rather than creating, listing, testing, or rotating one. However, it provides no explicit when-to-use/when-not-to-use guidance and does not reference alternatives like tailscale_create_webhook or tailscale_delete_webhook.

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