Skip to main content
Glama

skycloak_delete_login_branding

Destructive

Revert a Keycloak realm's login branding to default settings; set confirm=true to proceed.

Instructions

Revert login branding to defaults. Set confirm=true to proceed.

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": {
      "cluster_id": "<cluster_id>",
      "realm": "<realm>",
      "confirm": "<confirm>"
    },
    "name": "skycloak_delete_login_branding"
  }
}

Input Schema

NameRequiredDescriptionDefault
realmYesthe Keycloak realm name
confirmYesmust be true to confirm deletion
cluster_idYesthe cluster ID

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the danger profile is covered. The description adds the meaningful behavioral fact that custom branding is discarded in favor of defaults, plus the confirmation gate. It omits whether the revert is recoverable or what happens when no custom branding exists.

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?

Two short sentences, front-loaded with the effect and followed by the required gate. No redundant or promotional wording; every clause carries information.

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?

With rich annotations, a fully described three-parameter schema and an output schema, the description covers the essentials for a destructive revert. The only minor gap is guidance on alternatives and preconditions such as reading current branding before discarding it.

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 100%, with realm, cluster_id and confirm each documented, including that confirm 'must be true to confirm deletion'. The description merely repeats the confirm requirement and adds no scoping or format meaning beyond the schema, so the baseline applies.

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?

States a specific verb and resource: 'Revert login branding to defaults'. An agent can distinguish it from skycloak_upsert_login_branding and skycloak_delete_email_branding because the resource and the 'to defaults' outcome are named. It stops short of explicitly contrasting with the sibling upsert tool, which is why it is not a 5.

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?

Usage is implied by the name and the 'revert to defaults' phrasing, and a procedural prerequisite (confirm=true) is given. However, it never says when to choose this over skycloak_upsert_login_branding or whether branding should be read first, so the agent must infer the decision boundary.

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

Deploy Server

Other Tools