Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

Delete API Key

deleteAPIKey
Destructive

Permanently deletes an Uptime Kuma API key so any service still using it is denied access. Use listAPIKeys to find the key ID first.

Instructions

Permanently deletes an API key: anything still using it is refused from then on. To switch it off but keep it, use setAPIKeyActive. Find the ID with listAPIKeys.

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": {
      "keyID": "<keyID>"
    },
    "name": "deleteAPIKey"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIDYesThe ID of the API key to delete

Output Schema

NameRequiredDescriptionDefault
okYes
msgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: the deletion is permanent and existing consumers of the key will be refused going forward. It does not cover permissions required, whether confirmation is needed, or the fact that the operation is not idempotent per annotations, so it stops short of 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?

Three short sentences, zero waste: the destructive consequence is front-loaded, the safer alternative follows, and the ID discovery hint comes last. Nothing could be removed without losing guidance.

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?

For a single-parameter destructive tool with full schema coverage and an output schema, the description supplies everything an agent needs: effect, irreversibility, the safer sibling, and where to get the ID. Return values need not be explained because an output schema exists.

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

Parameters4/5

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

Schema coverage is 100% and the single keyID parameter is fully described there, so the baseline is 3. The description adds provenance the schema lacks by pointing to listAPIKeys as the way to obtain a valid keyID, which is genuinely useful for a destructive call.

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?

"Permanently deletes an API key" gives a specific verb plus resource, and the following clause defines the exact consequence (anything still using it is refused). It is clearly distinguishable from the sibling setAPIKeyActive, which the description names as the non-destructive counterpart.

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?

Explicit when-to-use and when-not-to-use guidance: choose this for permanent removal, choose setAPIKeyActive to merely disable while keeping the key. It also tells the agent how to source the required ID via listAPIKeys, removing the most likely invocation failure.

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