Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete user invite

tailscale_delete_user_invite
DestructiveIdempotent

Deletes a Tailscale user invite by ID, immediately revoking the invite link. Use this irreversible action to cancel pending invitations.

Instructions

Delete a user 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_user_invite"
  }
}

Input Schema

NameRequiredDescriptionDefault
inviteIdYesThe user 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, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description usefully adds the concrete consequence of destruction — 'the invite link will stop working' — which tells the agent what actually breaks, though it says nothing about auth/permission requirements or behavior when the invite is already accepted or expired.

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, action first and consequence second, with zero filler. Nothing could be removed without losing information.

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 single-parameter destructive tool with rich annotations and no output schema, this is nearly complete: the action, its irreversibility, and the user-facing effect are all stated. The only meaningful gap is how to source the inviteId and what happens if the invite is no longer pending.

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 coverage is 100% and the single inviteId parameter is documented in-schema as 'The user invite ID to delete'. The description adds nothing beyond that, notably not where to obtain the inviteId (e.g., via tailscale_list_user_invites), so the baseline 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 states a specific verb and resource ('Delete a user invite'), which is unambiguous and distinguishable from the nearby tailscale_delete_device_invite by naming the resource as a *user* invite. It stops short of an explicit contrast sentence, but an agent can route correctly from the name plus the description.

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 or when-not-to-use guidance and no alternative named. The relevant siblings (tailscale_resend_user_invite, tailscale_delete_device_invite, tailscale_list_user_invites) are never referenced, so the choice between revoking versus resending an invite is left entirely to inference.

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