Skip to main content
Glama

Update Team Member Role

team_update_member_role

Change an existing team member's role to admin, member, or viewer within a workspace so access permissions stay current.

Instructions

Update the role of an existing team member. Requires TEAM_DB_PATH.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "team_update_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoThe new role to assign (admin, member, viewer)
authorNoThe author ID/username to update
workspace_idNoOptional workspace isolation identifier (e.g. "alpha"). Do not use numeric project IDs or "workspace" as the key.

Output Schema

NameRequiredDescriptionDefault
codeNoError code (e.g. VALIDATION_ERROR, INTERNAL_ERROR)
errorNoHuman-readable error message
memberNo
detailsNoAdditional error context
successYes
categoryNoError category (validation, query, connection, internal)
suggestionNoSuggested fix for the error
recoverableNoWhether the error is recoverable
aggregated_errorsNoDetails of individual errors in a multi-step operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv9.1.0
    • changedInput schema / properties / role / description
      Previous value: -"The new role to assign"New value: +"The new role to assign (admin, member, viewer)"
    • removedInput schema / properties / role / enum
      Removed value: -[
      -  "admin",
      -  "member",
      -  "viewer"
      -]
    • removedInput schema / required
      Removed value: -[
      -  "author",
      -  "role"
      -]
  2. First observedv9.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent write, so the description adds little beyond the TEAM_DB_PATH prerequisite. It doesn't mention who may change roles, whether an invalid role fails or is coerced, or what happens to the member's existing permissions and entries – all material for a permission-changing mutation with idempotentHint=false.

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?

Two short sentences, front-loaded with the action, and no filler. It is efficient but so sparse that nothing is highlighted beyond the prerequisite.

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?

An output schema exists so return values need no explanation, and all three parameters are well documented in the schema. However, for a privilege-changing operation the description omits authorization expectations, effect on the member's access, and error behavior – the areas structured fields don't cover.

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%, including the enumerated role values and the workspace_id isolation warning, so the schema carries the parameter burden. The description adds no parameter meaning of its own, which is the baseline case when coverage is complete.

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?

States a specific verb and resource ("Update the role of an existing team member"), which clearly separates it from team_add_member and team_remove_member in the sibling list. It stops short of naming those siblings explicitly, so differentiation is inferred rather than declared.

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?

No when-to-use or when-not-to-use guidance. It does not say to use team_add_member first for new members, or team_remove_member instead of demoting to a non-member role, so the agent must guess the boundary against at least three adjacent siblings.

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