Skip to main content
Glama
shigechika

keycloak-mcp

by shigechika

get_admin_events

Retrieve Keycloak admin events to view operations performed by admins, such as user attribute updates, role assignments, and client configuration changes. Useful when user events do not reflect the changes.

Instructions

Get KeyCloak admin events (changes performed via the Admin REST API).

Admin events record operations performed by service accounts or admin users — e.g. custom user attribute updates (temp_password), role / group assignments, client configuration changes. These are distinct from user events (login / password change). Use this when UPDATE_PROFILE in get_events is empty but an attribute is known to have changed.

Args: operation_types: Comma-separated list of CREATE, UPDATE, DELETE, ACTION. resource_types: Comma-separated list of USER, CLIENT, ROLE, GROUP, REALM_ROLE, etc. resource_path: Filter by resource path (e.g. "users/{userId}"). date_from: Start date (YYYY-MM-DD). Defaults to last 24h when omitted (KEYCLOAK_DEFAULT_DATE_FROM_HOURS). date_to: End date (YYYY-MM-DD). max_results: Maximum results (default 50). max_repr: Max chars of the representation field. 0 = omit, -1 = full.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operation_typesNo
resource_typesNo
resource_pathNo
date_fromNo
date_toNo
max_resultsNo
max_reprNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the purpose and data type (admin events vs user events), and notes default date range (last 24h). However, it does not explicitly state read-only nature or disclose rate limits or authentication needs, leaving some behavioral traits implicit.

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?

Well-structured with a one-line summary, explanatory paragraph, usage guidance, and a clear Args section. Each sentence adds value; no fluff.

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

Completeness5/5

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

All 7 parameters are fully described with defaults and special values. The description explains admin events concept, usage scenario, and output likely includes representation. With good annotations and output schema, this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description provides detailed semantics for all 7 parameters, e.g., 'Comma-separated list of CREATE, UPDATE, DELETE, ACTION' for operation_types, format for date_from, and special values for max_repr (0=omit, -1=full). Completely compensates for lack of schema descriptions.

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 clearly states the verb 'Get' and resource 'KeyCloak admin events (changes performed via the Admin REST API)'. It distinguishes admin events from user events by specifying they are operations by service accounts/admin users, differentiating from sibling tool 'get_events'.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool: 'Use this when UPDATE_PROFILE in get_events is empty but an attribute is known to have changed.' This contrasts with sibling 'get_events' and provides clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/shigechika/keycloak-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server