Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Get webhook

tailscale_get_webhook
Read-onlyIdempotent

Retrieve details for a specific Tailscale webhook using its webhook ID to inspect configuration and status.

Instructions

Get details for a specific webhook.

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

Input Schema

NameRequiredDescriptionDefault
webhookIdYesThe webhook ID

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

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that: no statement of what happens when the ID does not exist, whether secret material is redacted in the response, or any rate-limit or permission context. For a read tool the annotation bar is lower, but zero added context still warrants a 2.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with the resource and scope front-loaded and no filler. It is not verbose, though the brevity reflects under-specification rather than tight editing of richer content.

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?

This is a simple single-parameter getter with rich annotations and a fully documented schema, so little prose is required. With no output schema, however, the description never indicates what 'details' comprise (URL, subscriptions, creation metadata, secret visibility), leaving the return payload opaque.

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 'webhookId' documented as 'The webhook ID', so the schema carries parameter semantics on its own. The description adds no format hints (ID prefix, length, where to obtain the ID), which is acceptable at baseline but not value-adding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a verb ('Get') and resource ('webhook') with a scope qualifier ('a specific webhook'), so the basic purpose is legible. However, it is essentially a restatement of the title 'Get webhook' and never explicitly distinguishes itself from the sibling tailscale_list_webhooks; the by-ID versus listing distinction must be inferred from the single required 'webhookId' parameter.

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 when-to-use guidance, no mention of prerequisites (e.g. needing a known webhook ID), and no reference to alternatives such as tailscale_list_webhooks or tailscale_get_log_stream_config. An agent must infer the calling context entirely from the tool name and schema.

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