Skip to main content
Glama

update_workspace_member

Destructive

Update a member's role in a specific workspace by workspace_id and user_id. Confirm the current assignment first; only the role changes to admin, member, or manager.

Instructions

Update a workspace member's role by workspace_id and user_id. Only the role changes here; use list_workspace_members or get_workspace_member to confirm the current assignment first.

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": {
      "workspace_id": "<workspace_id>",
      "user_id": "<user_id>",
      "role": "<role>"
    },
    "name": "update_workspace_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYesNew role in the workspace
user_idYesThe user ID to update (must be a valid UUID from list_all_users, not an email address)
workspace_idYesThe workspace ID

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed1 schema field changedv1.0.11
    • addedInput schema / properties / workspace_id / minLength
      Added value: +1
  3. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Changed3 schema fields changedv1.0.5
    • changedInput schema / properties / user_id / description
      Previous value: -"The user ID to update"New value: +"The user ID to update (must be a valid UUID from list_all_users, not an email address)"
    • addedInput schema / properties / user_id / format
      Added value: +"uuid"
    • addedInput schema / properties / user_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  5. Addedv1.0.1
  6. Removed
  7. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds useful mitigation context by implying verification before mutation and by scoping the change to the role only, but it omits whether the caller needs admin rights, what happens when roles are downgraded, and what errors occur if the user is not a member.

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 sentences, front-loaded with the mutation scope before the prerequisite, and no redundant restatement of the title or parameter names.

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 three-parameter mutation with an output schema and full annotation coverage, the definition supplies the scope and a verification workflow. Authorization requirements and side effects of a role change remain undocumented, which keeps it just short of complete.

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%, with an enum on role and a UUID pattern on user_id, so the schema does the heavy lifting. The description reinforces that the two IDs select the member and that only role is mutated, but adds no format, default, or constraint detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update a workspace member's role') plus the exact identifying keys (workspace_id, user_id), and explicitly narrows scope with 'Only the role changes here', which separates it from update_workspace and add/remove_workspace_member.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names two concrete read alternatives (list_workspace_members, get_workspace_member) and gives a precondition for using them ('confirm the current assignment first'). It does not explicitly say when not to use this tool, e.g. when the member is not yet in the workspace and add_workspace_member is the right call.

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