keycloak-mcp-server

list-identity-providers

List identity providers in a Keycloak realm. Supports search filtering, pagination, and result limits for efficient lookup.

Instructions

List all identity providers in a realm

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": "list-identity-providers"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. It only restates the tool's name without explaining pagination, search behavior, sorting, or return format, leaving the agent uncertain about how the operation behaves beyond the obvious listing.

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 sentence, front-loaded with the action and resource, and free of unnecessary words. It is as concise as possible while conveying the core purpose.

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

Completeness2/5

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

With 4 parameters, no annotations, and no output schema, the description is insufficient. It fails to explain how max, first, and search interact, what the response contains, or whether 'all' means literally all or requires pagination. This leaves significant gaps for an agent to invoke the tool effectively.

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 schema covers all parameters with descriptions, so the baseline is 3. The tool description adds no additional meaning; however, the phrase 'all identity providers' conflicts with the presence of max/first/search parameters, subtly implying pagination but not explaining it.

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 action ('List') and the resource ('identity providers') with a scope ('in a realm'), which distinguishes it from sibling tools like list-identity-provider-mappers and list-realms. The purpose is immediately understandable.

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

Usage Guidelines3/5

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

The description implies usage but provides no explicit guidance on when to choose this tool over alternatives. It doesn't mention exclusions or how it relates to get-identity-provider or list-identity-provider-mappers, making the context clear but not fully defined.

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

Deploy Server