Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Update user role

tailscale_update_user_role
Idempotent

Assign a new role to a tailnet user by providing their user ID and desired role, enabling permission updates for owners, admins, auditors, or members.

Instructions

Update a user's role in the tailnet.

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": {
      "userId": "<userId>",
      "role": "<role>"
    },
    "name": "tailscale_update_user_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesThe new role to assign
userIdYesThe user ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / userId / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds nothing beyond that: it does not mention the privilege implications of granting owner/admin, whether the acting caller needs a specific role, or whether invalid/downgrade attempts fail. For a permission-mutating tool, that is a real gap.

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

Conciseness3/5

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

The single sentence is front-loaded and free of filler, so there is no wasted wording. However, the brevity here reflects under-specification rather than economy, leaving the definition thin relative to the operation's impact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is structurally simple (two required params, full schema coverage, no output schema), but it performs a privileged permission change with no stated authorization requirements or failure conditions. Annotations cover safety hints, yet nothing tells the agent what an incorrect call could do to tailnet access.

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 role parameter carries an explicit enum with a description, so the schema already carries the parameter meaning. The description contributes no additional semantics such as ordering, defaults, or the effect of each role, so the baseline 3 applies.

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?

"Update a user's role in the tailnet" states a verb (update) and a resource (user role), but it is essentially a restatement of the title "Update user role" with only a scope qualifier added. It gives no hint of what a role change entails or how it differs from adjacent user-lifecycle siblings like tailscale_approve_user or tailscale_suspend_user.

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., that only owners/admins can assign privileged roles), and no routing to alternatives such as tailscale_get_user to inspect a current role first. The agent must infer everything about applicability.

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