Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete device invite

tailscale_delete_device_invite
DestructiveIdempotent

Permanently delete a Tailscale device invite by ID, revoking the invite link so it can no longer be used.

Instructions

Delete a device invite. This is irreversible -- the invite link will stop working.

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": {
      "inviteId": "<inviteId>"
    },
    "name": "tailscale_delete_device_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesThe device invite ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / inviteId / 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 and idempotentHint=true, so the safety profile is known; the description nonetheless adds concrete consequence detail that the annotations cannot convey — the operation is irreversible and the invite link stops working. It omits edge behavior such as the effect on devices that already redeemed the invite, which keeps it off 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 padding; the action is stated first and the irreversible consequence is front-loaded immediately after so an agent reads the risk before acting.

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 one-parameter deletion with full schema coverage, rich annotations, and no output schema, the description covers purpose and consequence adequately. A note on what happens to already-accepted invites, or an explicit pointer to tailscale_list_device_invites for discovering IDs, would make it 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?

Schema description coverage is 100% for the single required parameter, and its description ('The device invite ID to delete') is self-explanatory. The tool description adds no format, sourcing, or lookup guidance beyond the schema, so the baseline of 3 applies.

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 uses a specific verb and resource ('Delete a device invite'), which cleanly separates it from siblings such as tailscale_delete_user_invite, tailscale_get_device_invite, and tailscale_delete_device. It stops short of explicitly naming those siblings, so differentiation relies on the agent reading the name.

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 prerequisites, and no mention of alternatives (for example, whether to revoke versus delete, or what to do if the invite was already accepted). The agent must infer the context entirely from the tool name.

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