Skip to main content
Glama

Remove user from organization

remove_user
DestructiveIdempotent

Permanently remove an organization member. This action is IRREVERSIBLE — the user must be re-invited to rejoin. Returns a preview; re-call with the confirm_token and an idempotency_key to commit.

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": {
      "org_user_id": "<org_user_id>"
    },
    "name": "remove_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
org_user_idYesId of the OrganizationUser record to remove (not the Firebase userId).
confirm_tokenNoToken returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
idempotency_keyNoRequired when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds real value: it spells out that the removal is irreversible, that recovery requires re-invitation, and that the operation is a two-step preview-then-commit flow. It also explains the idempotency guarantee's purpose (retries return the original result instead of acting twice), which is behavioral context not captured by the boolean hint.

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?

Three short sentences, front-loaded with the destructive consequence before the mechanics of committing. No filler; every clause conveys either risk or invocation procedure.

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 destructive mutation with no output schema, the description covers irreversibility and the full commit workflow, which is what an agent most needs. It leaves out authorization requirements and what the preview payload shows, but these are secondary given the rich schema descriptions.

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 workflow-level meaning the schema does not state as a whole: the first call returns a preview, and the commit requires both confirm_token and idempotency_key together. That sequencing context is genuinely useful beyond the per-field descriptions.

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

Purpose4/5

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

States a specific verb and resource ("Permanently remove an organization member") and adds the distinguishing qualifier "permanently" plus the irreversibility consequence, which separates it in spirit from reversible siblings like disable_user. It does not explicitly name a sibling alternative, keeping it just short of a 5.

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

Usage Guidelines3/5

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

The word "Permanently" and the note that the user must be re-invited imply this is for hard removal rather than temporary suspension, and the preview/commit instruction tells the agent how to invoke it. However, no explicit when-to-use versus siblings such as disable_user or remove_user_from_customer is given, so the routing guidance is inferred rather than stated.

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