Skip to main content
Glama

Delete a domain API key

delete_domain_api_key
Destructive

Permanently deletes a domain API key so any caller using it immediately receives 401 errors. Requires confirm=true; call once without confirm to preview the deletion first.

Instructions

Permanently deletes a domain API key — any caller using it starts getting 401s immediately. This cannot be undone (unlike update_domain_api_key's isActive:false, which is reversible). Requires confirm=true — first call WITHOUT confirm to preview, then again with confirm:true.

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": {
      "domainId": "<domainId>",
      "keyId": "<keyId>"
    },
    "name": "delete_domain_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyIdYesThe key's id — from list_domain_api_keys.
confirmNoMust be true to delete. Omit/false returns a preview only.
domainIdYesThe domain's id — from list_domains.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.53.0

TDQS

A4.5/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true, but the description adds real value the annotation cannot: callers using the key get 401s immediately, and the effect is irreversible. That said, the irreversibility contrast and confirm flow are the only additional traits; nothing is said about side effects on audit records, dependent resources, or error behavior when the key is already gone.

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 sentences, each earning its place: what it does and its immediate effect, irreversibility with a contrast to the reversible sibling, then the confirm protocol. Front-loaded with the consequence and zero padding.

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?

No output schema exists and none is needed for a deletion that returns a preview or confirmation. With 100% schema coverage and a destructive annotation, the description supplies everything an agent needs to call this safely, including the guardrail against accidental permanent deletion.

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%, so the baseline is 3, but the description adds operational meaning beyond the schema's field-level note by making the preview-then-confirm sequencing an explicit protocol. domainId and keyId semantics are left entirely to the schema, which is acceptable since they are fully documented.

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?

States a specific verb and resource ("Permanently deletes a domain API key") and immediately scopes the blast radius. It distinguishes itself from update_domain_api_key's reversible deactivation, so an agent can pick the right tool without opening either schema.

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 names the alternative (update_domain_api_key with isActive:false) and the condition under which it is preferable, and prescribes the two-call pattern: preview without confirm, then confirm:true. Both the when and the when-not are covered.

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