Skip to main content
Glama

skycloak_delete_email_branding

Destructive

Revert a Keycloak realm's custom email branding to default settings; set confirm=true to proceed with the reset.

Instructions

Revert email 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_email_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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by saying what is actually destroyed — custom branding is replaced with defaults, not merely removed — plus the explicit confirm gate that must be satisfied before the write occurs. It does not mention permissions or reversibility of the revert, keeping it off a 5.

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, the outcome statement front-loaded and the safety gate second. Nothing is padded and every sentence carries information an agent needs.

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 three-parameter, single-objective mutation with rich annotations and an output schema, the description covers the essential outcome and the confirm requirement. Permissions requirements and what the response contains after the revert are left to the schema and annotations, which is acceptable here.

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 inline, so the baseline is 3. The description only restates the confirm=true requirement that the schema already spells out, adding no new semantics for realm or cluster_id scope.

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 email branding to defaults.' This clearly separates it from sibling write tools such as skycloak_upsert_email_branding and from skycloak_delete_login_branding by naming the email-branding resource. It stops short of explicitly naming the alternative tool an agent should pick instead, so it lands at 4 rather than 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?

The 'Set confirm=true to proceed' sentence gives an operational precondition but no when-to-use or when-not-to-use guidance relative to siblings (get/upsert email branding, or the login-branding counterparts). Usage is implied by the destructive 'revert' verb but never spelled out.

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