@mgcrea/mcp-keycloak

keycloak_list_admin_events

Read-only

Audit realm changes by searching admin events for user, client, and role modifications. Filter by date, user, client, resource path, or operation type.

Instructions

Search admin events — the audit trail of changes made to the realm itself (who created this user, who changed that client). Requires admin event logging to be enabled.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "keycloak_list_admin_events"
  }
}

Input Schema

Name	Required	Description
`max`	No	Maximum number of results to return (1-500). Defaults to 50.
`first`	No	Pagination offset — index of the first result to return (0-based).
`realm`	No	Realm to operate on. Defaults to the server's configured realm (KEYCLOAK_REALM).
`dateTo`	No	Inclusive upper bound, as YYYY-MM-DD.
`authUser`	No	Filter by the user UUID that made the change.
`dateFrom`	No	Inclusive lower bound, as YYYY-MM-DD.
`authClient`	No	Filter by the clientId that made the change.
`resourcePath`	No	e.g. `users/8f3c...`.
`resourceTypes`	No	e.g. ["USER", "CLIENT", "REALM_ROLE", "GROUP"].
`operationTypes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, lowering the burden. The description adds non-obvious behavioral context by noting that admin event logging must be enabled for the query to be meaningful, and frames the result as audit-trail data. It does not describe return shape or behavior when logging is disabled, but the prerequisite is a valuable disclosure.

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 one tight sentence that leads with the core action, defines the resource, gives concrete examples, and adds a necessary prerequisite. Every clause earns its place; there is no filler.

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

Completeness4/5

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

For a read-only list/search tool with a rich schema covering most of the 10 parameters, this description is largely sufficient. It provides the domain framing and prerequisite, while the schema handles filters and paging. It could be more complete about return value assumptions and ordering, but no output schema exists and the described scope is clear.

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 90%, so the schema already documents most parameters. The description's examples ('who created this user, who changed that client') loosely map to authUser/authClient filters but add no direct parameter-level details beyond what the schema provides. Baseline 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 uses a specific verb ('Search') with a specific resource ('admin events') and defines what those are: the audit trail of realm changes. It provides concrete examples and conceptually distinguishes this from keycloak_list_events, which covers user events.

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

Usage Guidelines4/5

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

The description gives clear context for when to use this tool: for changes made to the realm itself, not user-level activity. It also includes a prerequisite ('Requires admin event logging to be enabled'). It does not explicitly name alternatives or conditions under which another tool should be used, so it stops short of a 5.

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

Deploy Server