Skip to main content
Glama

Manage members

manage_members
Destructive

Ask to invite someone to a project, change a member's role, or remove a member. To see who is on it use list_project_items item members. No call changes membership itself: each files a request that the person behind this token, an owner of the project, confirms in the web app with a second factor; the server then makes exactly that change, once. Show approveUrl to the user, then call get_access_requests with the request id and wait; it answers done once the change is made. Actions (arguments besides action, project and reason):

  • invite (email, role): an invitation is emailed once confirmed; the person joins when they accept it.

  • set_role (member, role) and remove (member): member is an id from list_project_items item members, or the member's email. Removing a member also ends their agents' access to the project. Errors are messages: a member not on the project, inviting a current member, changing a member who only sees shared items, removing or demoting the last owner, an archived project, a server that cannot send email, too many requests waiting, a CI job's token, and, where billing is on, an organisation not on Pro. Audited. Needs projects:write, the owner role and full access to the project.

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>",
      "project": "<project>",
      "reason": "<reason>"
    },
    "name": "manage_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoinvite, set_role: reader (reads), editor (also writes) or owner (also manages members and settings)
emailNoinvite only: the address the invitation goes to
actionYesWhat to ask for
memberNoset_role, remove: the member's user id (id from list_project_items item members) or their email
reasonYesOne sentence the owner reads when confirming: what you are doing and why
projectYesProject slug from list_projects, e.g. my-app, or its id (a UUID)
answer_withinNoMinutes the owner has to confirm (1 to 60, default 10)

Output Schema

NameRequiredDescriptionDefault
nextNodelete (manage_projects), invite, set_role, remove: what to do next
actionNodelete (manage_projects), invite, set_role, remove: the change the owner is asked to confirm (kind, plus email, userId and role where they apply)
statusNodelete (manage_projects), invite, set_role, remove: always "pending" here
requestNodelete (manage_projects), invite, set_role, remove: the request id to pass to get_access_requests
answerByNodelete (manage_projects), invite, set_role, remove: when the request expires unanswered
approveUrlNodelete (manage_projects), invite, set_role, remove: show this to the user; they confirm there with a second factor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "action": {
      +      "additionalProperties": {},
      +      "description": "delete (manage_projects), invite, set_role, remove: the change the owner is asked to confirm (kind, plus email, userId and role where they apply)",
      +      "properties": {
      +        "kind": {
      +          "description": "delete_project, invite_member, set_member_role or remove_member",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "kind"
      +      ],
      +      "type": "object"
      +    },
      +    "answerBy": {
      +      "description": "delete (manage_projects), invite, set_role, remove: when the request expires unanswered",
      +      "type": "string"
      +    },
      +    "approveUrl": {
      +      "description": "delete (manage_projects), invite, set_role, remove: show this to the user; they confirm there with a second factor",
      +      "type": "string"
      +    },
      +    "next": {
      +      "description": "delete (manage_projects), invite, set_role, remove: what to do next",
      +      "type": "string"
      +    },
      +    "request": {
      +      "description": "delete (manage_projects), invite, set_role, remove: the request id to pass to get_access_requests",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "delete (manage_projects), invite, set_role, remove: always \"pending\" here",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Far beyond the annotations, it discloses that no call mutates membership directly — each files a request the token owner confirms with a second factor, applied exactly once — plus an explicit error catalog (last owner, archived project, email failure, rate limiting, CI token, billing) and an audit note. This is the critical behavioral context that destructiveHint=true alone cannot convey.

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 core action, then the confirmation workflow, then a compact per-action bullet list. Dense but nearly every sentence carries operational meaning; the error enumeration is long yet useful, so only minor trimming is conceivable.

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?

Given seven parameters, an output schema, and a destructive async approval workflow, the description covers invocation, sequencing, permissions, error modes, and side effects. Nothing an agent needs to call it correctly or to explain the pending-approval state to a user is missing.

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 action-to-parameter mapping the schema cannot express: email belongs to invite, member to set_role/remove, role to invite/set_role, and member may be an id from list_project_items or an email. It also explains the semantic consequence of remove (their agents lose access).

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?

The opening sentence names the exact verb+resource set (invite, change role, remove member) and the bullet list enumerates each action with its arguments. It explicitly distinguishes itself from list_project_items, which handles read-only member listing.

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?

It states when to use this tool versus the alternative ('To see who is on it use list_project_items item members') and gives the required preconditions: projects:write, owner role, full project access. It also tells the agent the mandatory follow-up sequence (show approveUrl, then call get_access_requests with the request id and wait).

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