keycloak-mcp-server

create-group

Create a new user group in a Keycloak realm by providing name and optional parent group ID.

Instructions

Create user groups

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>",
      "name": "<name>"
    },
    "name": "create-group"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Group name
`realm`	Yes	Realm name
`parentId`	No	Parent group ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description offers no additional behavioral context. It doesn't disclose permission requirements, the significance of 'parentId' (e.g., whether it creates a subgroup), or any side effects beyond the creation itself.

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, direct sentence that immediately conveys the purpose without unnecessary elaboration. It earns its place by being clear and to the point.

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?

The tool has a simple create operation and the schema covers parameters fully. However, the description doesn't explain the optional 'parentId' relationship to sibling tool 'create-child-group', nor what the tool returns, making it only minimally complete for an agent to use correctly.

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 already provides descriptions for all 3 parameters, covering 100% of them. The description adds no extra semantics or usage tips beyond what the schema states, which is acceptable given the high coverage.

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 'Create user groups' clearly states the action (create) and the resource (user groups), making the tool's function obvious. However, it doesn't differentiate from the sibling tool 'create-child-group', leaving ambiguity about whether this handles top-level groups only.

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 'create-child-group' or 'create-role'. The description lacks any exclusions or contextual hints for choosing this tool.

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

Deploy Server