Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Delete posture integration

tailscale_delete_posture_integration
DestructiveIdempotent

Delete a Tailscale posture integration by ID to permanently remove it. Use this when the integration is no longer needed; the action is irreversible.

Instructions

Delete a posture integration. This is irreversible.

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": {
      "integrationId": "<integrationId>"
    },
    "name": "tailscale_delete_posture_integration"
  }
}

Input Schema

NameRequiredDescriptionDefault
integrationIdYesThe posture integration ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / integrationId / 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 mark the tool as destructive, but the description adds meaningful context by stating that the deletion is irreversible. It does not cover authorization requirements or downstream effects on related posture attributes, but the irreversibility warning is valuable.

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 the operation and key risk front-loaded. There is no redundant wording, and the critical warning follows immediately.

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 delete operation with rich annotations and full schema coverage, the definition provides enough context to invoke the tool correctly. It could say more about related resources affected by deletion, but the core behavior and irreversible nature are clear.

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?

The schema has full description coverage and documents the sole required 'integrationId' parameter. The description adds no parameter detail beyond the schema, so the baseline score 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 names a specific verb and resource: 'Delete a posture integration.' An agent can identify the operation immediately, though it does not explicitly distinguish this tool from sibling posture-integration tools such as get/update/list.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. It is clear that this is a deletion action, but it does not explain when to choose it over updating or otherwise disabling an integration.

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