Skip to main content
Glama

Remove user from project

remove_user_project
DestructiveIdempotent

Remove an organization member's assignment from a specific project. The user will no longer have direct visibility to that project (they may still see it via a customer assignment). Requires org_user_id and project_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself. Requires confirm=true to proceed.

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>",
      "project_id": "<project_id>"
    },
    "name": "remove_user_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true to perform the action. Omit or false returns a preview only — nothing is written.
project_idYesId of the project to remove the user from.
org_user_idYesId of the OrganizationUser to remove from the project (not the Firebase user id).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm
      Added value: +{
      +  "description": "Set true to perform the action. Omit or false returns a preview only — nothing is written.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (destructive, idempotent), the description discloses the actual effect — the user loses direct visibility to the project but may retain access via a customer assignment — plus a privilege-boundary constraint and the confirm gate. These are the operational facts an agent needs before invoking a destructive mutation.

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?

Four compact sentences, each carrying a distinct constraint or consequence, with the primary effect stated first and safeguards following. No filler or restatement of the title.

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, confirm-gated mutation with full annotation coverage and full schema coverage, the description supplies the missing pieces: real-world consequence, privilege limits, and scope-of-org behavior. Nothing an agent needs to call it safely appears to be absent.

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; the description adds value by stating the organization is fixed by context and must never be passed as a parameter, plus reinforcing the required org_user_id/project_id pair. It adds modest meaning beyond the schema rather than a lot.

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 — removing an org member's assignment from a specific project — and clarifies the consequence (loss of direct visibility) and the customer-assignment exception, which separates it from remove_user_from_customer and remove_user.

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?

Gives concrete preconditions (requires org_user_id and project_id, confirm=true, cannot target a more privileged user) and scope guidance (org fixed by context, never pass an org id). It doesn't explicitly route the agent to a sibling when the intent is customer-level rather than project-level removal, so it falls short of a 5.

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