Skip to main content
Glama

Change a team member's role

change_member_role
DestructiveIdempotent

Gives a team member (list_members) a new role and scope: manager (everything; with scope "all" also the team and plan), editor (writes and schedules posts, answers comments) or viewer (read only); scope "all" or workspace ids. It can hand out write access, so it first needs a manager's OK in Shager: the call answers needs_confirmation with confirm_url; after they approve, make the same call again. The owner's role never changes, a person can't change their own, and the team always keeps at least one manager with every workspace. Someone who stops being a full manager loses the API keys they created. (Not available in an unclaimed sandbox.)

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": {
      "member_id": "<member_id>",
      "role": "<role>"
    },
    "name": "change_member_role"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
scopeNo"all", or the workspace ids they may openall
member_idYesFrom list_members
confirmation_tokenNoThe confirmation_token from needs_confirmation. The call goes through only after your human approved this exact action at confirm_url.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the two-step confirmation handshake, the invariant rules (owner's role fixed, no self-change, at least one manager must remain), the side effect that demoted managers lose their API keys, and the sandbox restriction. This is rich context an agent cannot get from destructiveHint/idempotentHint alone.

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?

Purpose is front-loaded and every sentence carries information; the parenthetical sandbox note is placed well. It is dense and slightly long, but no sentence is filler.

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

Completeness5/5

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

For a destructive mutation with no output schema, the description supplies exactly what is missing: the non-standard needs_confirmation response shape, the retry procedure, invariants that can cause failure, and the permission-loss side effect. An agent could invoke and recover from this call correctly from this text.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaning the schema cannot: role semantics (manager = everything, editor = writes/schedules/answers comments, viewer = read only) and the special case that scope 'all' grants team and plan visibility only for managers. With 75% schema coverage the remaining gap is minor, though confirmation_token's lifecycle is restated rather than explained further.

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 ('Gives a team member ... a new role and scope') and enumerates the three role values with their meanings, so it is immediately distinguishable from siblings like invite_member, remove_member, and list_members.

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?

Explains the prerequisite approval flow in concrete terms (first call returns needs_confirmation with confirm_url, then repeat the same call) and names list_members as the source of member_id. It does not explicitly contrast with invite_member/remove_member, so the routing guidance is strong but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources