keycloak-mcp-server

list-sub-groups

List subgroups of a parent group in Keycloak with filters for realm, search, and pagination to manage group hierarchies.

Instructions

List subgroups of a parent group

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>",
      "parentGroupId": "<parentGroupId>"
    },
    "name": "list-sub-groups"
  }
}

Input Schema

Name	Required	Description
`max`	No	Maximum results
`first`	No	First result index
`realm`	Yes	Realm name
`search`	No	Search term
`parentGroupId`	Yes	Parent group ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. 'List' implies a read-only operation, but the description does not disclose pagination behavior (max/first), search semantics, or whether subgroups are direct or recursive. It is not misleading but lacks depth.

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, concise sentence with no wasted words. Every term ('List', 'subgroups', 'parent group') is informative and necessary.

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 description is minimal. It covers the core purpose but lacks operational detail such as pagination, search, and return structure. Given there is no output schema and 5 parameters, a bit more context would help, but the tool is conceptually simple.

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 coverage is 100%, so all parameters are already described in the input schema. The description adds no additional parameter context, so it meets the baseline but does not enhance understanding.

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 uses a specific verb ('List') and resource ('subgroups of a parent group'), clearly distinguishing it from 'list-groups' which presumably lists top-level groups. The parent group relation is explicit, leaving no ambiguity about the tool's function.

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?

The description provides no guidance on when to use this tool versus alternatives like 'list-groups' or 'create-child-group'. It only states the core function, relying on the agent to infer usage context from the parameters and sibling names.

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

Deploy Server