Skip to main content
Glama

Delete DNS record

delete_dns_record
Destructive

Delete one DNS record from a domain's zone. It cannot be undone: note the record from list_dns_records first if it may need to come back. Take recordId from a list_dns_records call made just before (it is a position and shifts after changes). Resolvers can keep answering with the record up to its TTL. To change a value instead, use edit_dns_record. You MUST set confirm to 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": {
      "id": "<id>",
      "recordId": "<recordId>",
      "confirm": "<confirm>"
    },
    "name": "delete_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID
confirmYesMust be true to confirm this destructive operation
recordIdYesrecordId from a list_dns_records call made just before this one

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing irreversibility, the operational consequence that resolvers may keep answering until TTL expiry, and the non-obvious fact that recordId is a positional index that shifts after changes. These are exactly the traits an agent cannot infer from structured fields.

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?

Four short sentences, each carrying distinct information — scope, irreversibility, ID freshness, cache lag, alternative tool, confirm flag. Front-loaded with the action and consequences; no filler.

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 three-parameter destructive tool with no output schema, everything an agent needs is present: what it destroys, that it is irreversible, how to obtain a valid recordId, the TTL caveat, the safer alternative, and the mandatory confirm flag.

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 real meaning on top: recordId is a position rather than a stable key and therefore must be re-fetched immediately before deletion. The confirm=true requirement is repeated from the schema, which is redundant but harmless.

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?

Opens with a specific verb and resource scoped to a single record ("Delete one DNS record from a domain's zone"), which distinguishes it from add_dns_record, edit_dns_record, and list_dns_records without needing the 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 for a different intent ("To change a value instead, use edit_dns_record") and gives the precondition for calling this one: take recordId from a list_dns_records call made just before. That covers when to use, when not to, and the prerequisite step.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.