Skip to main content
Glama

Remove Organization Member

remove_organization_member
DestructiveIdempotent

Remove a member from the organization of the workspace the call acts in: they leave every workspace in it, and their API keys and connect links are revoked. The organization owner cannot be removed, only the owner can remove an organization admin, and you cannot remove yourself. Confirm with the user first, naming the member and the workspaces they will lose. Needs the members.manage permission, which Admin holds. The member who created the key, or the signed-in member, must also be an organization owner or admin (org-owner or org-admin); otherwise it fails with 403 permission_denied. Returns { success: true }.

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": {
      "userId": "<userId>"
    },
    "name": "remove_organization_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe member's userId from list_members
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to act in the workspace list_workspaces marks current. Use the same workspaceId for every call about the same workspace, since ids from one workspace (accounts, posts, uploads) do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultYesAn object with success: true once the member is removed from the organization.

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?

Beyond the destructive and idempotent annotations, the description details the consequences: leaving every workspace, revoking API keys and connect links, required members.manage permission, caller authorization requirements, and the exact 403 failure mode. It also states the return shape.

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?

The description is dense and front-loaded with the operation and its scope. Every sentence carries important constraints or consequences, though the first sentence is long and could be easier to scan.

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?

The definition is complete for a destructive membership-removal tool: it covers scope, authorization, edge cases, confirmation, failure behavior, and return value. With an output schema present, no further return-value explanation is needed.

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%, so both userId and workspaceId are already documented. The description adds contextual meaning about the organization being determined by the workspace, but does not add syntax or format details 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?

The description states a specific verb and resource, and defines the scope precisely: removing an organization member, which removes them from every workspace in that organization and revokes API keys and connect links. This clearly distinguishes the operation from sibling member-removal tools that likely act at workspace level.

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 gives explicit when-to-use constraints: the organization owner cannot be removed, only the owner can remove an organization admin, and users cannot remove themselves. It also requires user confirmation naming the member and affected workspaces, which is strong operational guidance.

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