keycloak-mcp-server

list-group-members

Retrieve all members of a specified group in a Keycloak realm, with optional pagination for large groups.

Instructions

List members of a 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>",
      "groupId": "<groupId>"
    },
    "name": "list-group-members"
  }
}

Input Schema

Name	Required	Description
`max`	No	Maximum results
`first`	No	First result index
`realm`	Yes	Realm name
`groupId`	Yes	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?

With no annotations, the description carries the full burden of disclosing behavioral traits. The verb 'List' implies a read operation, but it does not disclose pagination behavior, authorization requirements, or whether the result includes nested members. This is minimal behavioral context beyond the operation 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, front-loaded sentence with no wasted words. It fully captures the tool's core action without any unnecessary elaboration.

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?

For a simple list operation with fully documented parameters, the description is minimally adequate. However, it omits any mention of pagination, return format, or how it differs from organization-member listing, leaving some context gaps for an agent.

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%; all four parameters have descriptions in the schema, so the description does not need to explain them. The tool description adds no extra parameter meaning beyond the schema, matching the baseline of 3.

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 'List members of a group' uses a specific verb ('List') and resource ('members of a group'), clearly distinguishing it from sibling tools like list-groups. However, it lacks additional scope or context, such as pagination or realm handling, so it is clear but not as rich as the high calibration example.

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 when-to-use guidance is provided. The description does not mention when to prefer this over list-groups, list-organization-members, or manage-user-groups, nor does it state any exclusions or prerequisites.

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

Deploy Server