keycloak-mcp-server

update-user

Update user details such as email, name, username, or status within a Keycloak realm by specifying the user ID.

Instructions

Update user information in 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": "update-user"
  }
}

Input Schema

Name	Required	Description
`email`	No	Email address
`realm`	Yes	Realm name
`userId`	Yes	User ID
`enabled`	No	User enabled status
`lastName`	No	Last name
`username`	No	Username
`firstName`	No	First name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

C2.9/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 for behavioral disclosure. It only restates the action without mentioning whether updates are partial or full, whether the user must already exist, permission requirements, or side effects. This is a significant gap for a mutation tool.

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 a single, front-loaded sentence with no filler or irrelevant details. It is efficient, though it sacrifices important nuance in favor of brevity.

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

Completeness2/5

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

For a 7-parameter mutation tool with no output schema and no annotations, a one-sentence description is inadequate. It does not explain update semantics, error conditions, or how realm and userId relate, leaving the agent to infer critical context from the schema alone.

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 all parameters are already documented in the schema. The description adds no additional meaning beyond the generic phrase 'user information', providing no extra semantic value.

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?

The description uses a specific verb ('Update') and resource ('user information') with a scope ('in a specific realm'), clearly distinguishing it from create/delete/get/list user tools. It could further differentiate from set-user-attributes, but the core action is clear.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like set-user-attributes, create-user, or delete-user. There are no exclusions, prerequisites, or typical use cases mentioned.

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

Deploy Server