Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Update posture integration

tailscale_update_posture_integration
Idempotent

Update an existing Tailscale posture integration's credentials or configuration, including client ID, secret, tenant ID, and cloud ID, without recreating the integration.

Instructions

Update an existing posture integration's credentials or configuration.

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

Input Schema

NameRequiredDescriptionDefault
cloudIdNoUpdated cloud identifier (e.g. 'us-1', 'global', or provider FQDN)
clientIdNoUpdated client ID for the provider
tenantIdNoUpdated tenant ID
clientSecretNoUpdated client secret for the provider (omit to retain the existing secret). SENSITIVE: passed straight to Tailscale and not echoed back, but MCP clients may log the input value you supply.
integrationIdYesThe posture integration ID to update

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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether omitted fields are preserved, what happens to credentials mid-rotation, or what a successful update returns. The useful secret-retention note lives in the schema, not here.

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 front-loaded sentence with zero filler, which is structurally clean. It is arguably too terse for a credential-mutating tool, but nothing in the sentence is wasted.

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?

Annotations cover the safety profile and the schema fully documents all five parameters, so the description is not badly under-specified. However, for a mutation that touches provider secrets, it should at minimum state that unspecified fields are left unchanged and that only integrationId is required.

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%, so the schema already documents each of the five parameters, including that clientSecret is sensitive and may be omitted to retain the existing value. The description's phrase 'credentials or configuration' loosely maps to the credential fields but adds no syntax, defaults, or format detail beyond the schema.

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 ('Update an existing posture integration') and names the affected surface ('credentials or configuration'). It is clearly distinguishable from the sibling read/create/delete posture-integration tools by the word 'existing' plus 'update', though it never names those siblings explicitly.

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: nothing says when to update versus delete-and-recreate, no prerequisites (admin role, provider-side setup), and no mention of partial-update semantics. Usage is only implied by the word 'existing'.

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