Skip to main content
Glama
YawLabs

@yawlabs/tailscale-mcp

by YawLabs
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

tailscale_create_webhook

Create a webhook to send Tailscale event notifications to your HTTPS endpoint. Specify event subscriptions; save the returned signing secret immediately.

Instructions

Create a new webhook. The response includes the webhook's signing secret -- this is the only opportunity to capture it; save it immediately.

SECURITY: the response body contains the secret verbatim. MCP clients commonly persist tool responses to logs and conversation transcripts; treat this response as sensitive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointUrlYesThe HTTPS URL to send webhook events to
subscriptionsYesEvent types to subscribe to (at least one)

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.1/5.0
Behavior5/5

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

The description discloses a critical, non-obvious behavior: the response contains the signing secret and this is the only chance to capture it. It also warns that the response is sensitive and may be persisted in logs, which goes well beyond the annotations that only mark mutability and non-idempotency.

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 compact sentences plus a short SECURITY note convey exactly what is needed without filler. The primary purpose is front-loaded, and the security warning appears immediately after, making the structure efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter create operation with no output schema, the description covers the essential operational detail: capture the one-time signing secret immediately and treat the response as sensitive. Combined with fully documented schema parameters, nothing needed to invoke the tool correctly is missing.

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 the schema already explaining endpointUrl as an HTTPS URL and subscriptions as event types with at least one required. The description adds no further parameter-level meaning, so the baseline of 3 is appropriate.

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 opens with 'Create a new webhook,' a specific verb plus resource that clearly states the action. It distinguishes itself from sibling webhook operations like list/get/update/delete/rotate/test by name and by the creation focus.

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?

No guidance is given about when to choose this tool over alternatives such as updating, listing, or rotating webhooks. The only additional instruction ('save it immediately') concerns post-invocation handling rather than tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools