Skip to main content
Glama

Manage workspace members

manage_members
Destructive

Admin-only membership controls. list returns members and pending invites. invite adds/renews an email invite (default member; existing members refused); email_sent reports best-effort delivery. resend_invite renews by invite_id; revoke_invite withdraws. set_role never demotes the last admin. set_manager sets/clears a manager, rejecting self-reporting and cycles. set_read_scope (sees) and set_write_scope (edits/deletes) take own/team/all/null (role default), optionally include_reports; never admins. remove cannot target yourself or the last admin; records remain. Except list/revoke_invite, actions preview the person/change until confirm:true. This connection is bound to one membership; leave/switch your own workspace in the browser.

When to use: An admin manages membership, invitations or an individual's access.

Example: Invite sara@brightside.example as a manager.

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": {
      "action": "<action>"
    },
    "name": "manage_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoinvite (default member) and set_role: admin, manager, member or viewer.
emailNoinvite: the address to invite (lower-cased and trimmed).
actionYesWhat to do. One of: list | invite | resend_invite | revoke_invite | set_role | set_manager | set_read_scope | set_write_scope | remove.
confirmNotrue carries a change out; omitted or false previews it.
user_idNoset_role / set_manager / remove: the member's user_id from a list call.
invite_idNoresend_invite / revoke_invite: the pending invite's id from a list call.
manager_idNoset_manager: the manager's user_id, or null to clear the reporting line.
read_scopeNoset_read_scope: null follows the role.
write_scopeNoset_write_scope: null follows the role.
include_reportsNoScope actions: also everyone reporting up to this member.

Output Schema

NameRequiredDescriptionDefault
noteNo
actionNo
inviteNo
memberNo
appliedNo
invitesNo
membersNo
email_sentNo
requires_confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"list, invite, resend_invite, revoke_invite, set_role, set_manager, set_read_scope or remove. One of: list | invite | resend_invite | revoke_invite | set_role | set_manager | set_read_scope | remove."New value: +"What to do. One of: list | invite | resend_invite | revoke_invite | set_role | set_manager | set_read_scope | set_write_scope | remove."
    • changedInput schema / properties / confirm / description
      Previous value: -"invite / resend_invite / set_role / set_manager / remove: true carries the change out; omitted or false returns the preview and changes nothing."New value: +"true carries a change out; omitted or false previews it."
    • changedInput schema / properties / include_reports / description
      Previous value: -"set_read_scope: also everyone reporting up to this member."New value: +"Scope actions: also everyone reporting up to this member."
    • changedInput schema / properties / read_scope / description
      Previous value: -"set_read_scope: own, team, all, or null to follow the role's setting."New value: +"set_read_scope: null follows the role."
    • addedInput schema / properties / write_scope
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "One of: own | team | all.",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "set_write_scope: null follows the role."
      +}
    • changedOutput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "invite",
      -  "resend_invite",
      -  "revoke_invite",
      -  "set_role",
      -  "set_manager",
      -  "set_read_scope",
      -  "remove"
      -]New value: +[
      +  "list",
      +  "invite",
      +  "resend_invite",
      +  "revoke_invite",
      +  "set_role",
      +  "set_manager",
      +  "set_read_scope",
      +  "set_write_scope",
      +  "remove"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"list, invite, resend_invite, revoke_invite, set_role, set_manager or remove. One of: list | invite | resend_invite | revoke_invite | set_role | set_manager | remove."New value: +"list, invite, resend_invite, revoke_invite, set_role, set_manager, set_read_scope or remove. One of: list | invite | resend_invite | revoke_invite | set_role | set_manager | set_read_scope | remove."
    • addedInput schema / properties / include_reports
      Added value: +{
      +  "description": "set_read_scope: also everyone reporting up to this member.",
      +  "type": [
      +    "boolean",
      +    "string",
      +    "number"
      +  ]
      +}
    • addedInput schema / properties / read_scope
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "One of: own | team | all.",
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "set_read_scope: own, team, all, or null to follow the role's setting."
      +}
    • changedOutput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "invite",
      -  "resend_invite",
      -  "revoke_invite",
      -  "set_role",
      -  "set_manager",
      -  "remove"
      -]New value: +[
      +  "list",
      +  "invite",
      +  "resend_invite",
      +  "revoke_invite",
      +  "set_role",
      +  "set_manager",
      +  "set_read_scope",
      +  "remove"
      +]
  3. Changed2 schema fields changed
    • removedInput schema / properties / confirm / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / confirm / type
      Added value: +[
      +  "boolean",
      +  "string",
      +  "number"
      +]
  4. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  5. Changed10 schema fields changed
    • removedOutput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / invite / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / invite / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / invites / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / invites / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / member / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / member / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / members / items / additionalProperties
      Removed value: -{}
    • removedOutput schema / properties / members / items / propertyNames
      Removed value: -{
      -  "type": "string"
      -}
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With destructiveHint=true already declared, the description goes well beyond annotations: it discloses the preview-then-confirm:true gate for all mutating actions except list/revoke_invite, invariant protections (never demotes the last admin, cannot remove yourself, rejects self-reporting and cycles), that records remain after removal, and that invite email delivery is best-effort. These are behavioral traits an agent could not infer from the annotations.

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?

Front-loaded with the access constraint and each action's rule in a tight clause; the preview/confirm rule is sensibly placed after the action list. It is dense and telegraphic (semicolon-chained clauses), which costs a bit of readability, but nearly every clause earns its place.

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 10-parameter, multi-action admin tool with an output schema already present, the description covers the safety invariants, the confirmation gate, scope semantics, and the out-of-scope browser flow. An agent has everything needed to pick an action and call it safely without reading further docs.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: 'null' follows the role for scopes, scopes apply to own/team/all and 'never admins', include_reports pulls in the reporting chain, and invite defaults to member while refusing existing members. That is genuine added semantics, though a couple of fields (manager_id clearing, role enum) are only restated from 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?

Opens with a specific verb+resource ('Admin-only membership controls') and then disambiguates the multi-action surface by naming each action (list, invite, resend_invite, revoke_invite, set_role, set_manager, set_read_scope, set_write_scope, remove) with its effect. That granularity makes it clearly distinct from siblings like update_workspace or manage_approvals.

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

Usage Guidelines5/5

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

Explicit 'When to use' line scopes it to admins managing membership, invitations or individual access, plus a concrete example. It also names an exclusion and the alternative channel: 'This connection is bound to one membership; leave/switch your own workspace in the browser.' That is exactly the when/when-not/alternative framing.

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