keycloak-mcp-server

delete-user

Remove a user from a Keycloak realm permanently. Specify the realm and user ID to delete the user account and associated data.

Instructions

Delete a user from a specific realm

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": {
      "realm": "<realm>",
      "userId": "<userId>"
    },
    "name": "delete-user"
  }
}

Input Schema

Name	Required	Description	Default
`realm`	Yes	Realm name
`userId`	Yes	User ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states 'Delete a user', which is inherently destructive, but does not mention permanence, side effects (e.g., removing user sessions or cascading deletions), permission prerequisites, or reversibility. This is a significant gap for a mutation tool with no annotation support.

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?

The description is a single, front-loaded sentence that conveys the essential action and scope without any superfluous words. It is well-suited for quick parsing by an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (two required string parameters, no output schema), the description is minimally adequate. However, it lacks behavioral context such as whether the deletion is permanent, what happens to related entities, or any prerequisites, which would be helpful for complete understanding. It is not incomplete enough to warrant a 2, but not rich enough for a 4.

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?

The input schema covers 100% of the parameters with descriptions ('Realm name' and 'User ID'). The tool description does not add any additional semantic meaning beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the action ('Delete') and the resource ('a user from a specific realm'), making the tool's purpose distinct from sibling tools like update-user, get-user, or delete-realm. The addition of 'from a specific realm' provides contextual scoping that differentiates it from other deletion tools.

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 description implies usage for deleting a user in a realm, but it does not explicitly state when to use this tool versus alternatives (e.g., update-user to modify or logout-user to end sessions). No exclusions or alternative recommendations are provided, so the guidance is implied rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server