@kodim/mcp-cloudflare-dns

Delete DNS Record

delete_dns_record

Destructive

Permanently delete a DNS record by specifying zone ID and record ID. Confirm the record ID via list_dns_records first because deletion is irreversible.

Instructions

Permanently delete a DNS record. This action cannot be undone. Use list_dns_records first to confirm the record ID.

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": {
      "zone_id": "<zone_id>",
      "record_id": "<record_id>"
    },
    "name": "delete_dns_record"
  }
}

Input Schema

Name	Required	Description	Default
`zone_id`	Yes	The zone ID
`record_id`	Yes	The DNS record ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already mark destructiveHint=true, and the description adds specificity with 'cannot be undone' and 'permanently', reinforcing the irreversible nature beyond the boolean hint.

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 sentences, front-loaded with the action, then the irreversible warning, then the prerequisite. Every word earns its place.

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?

The tool has simple parameters and no output schema, and the description covers purpose, irreversibility, and a preparation step. It lacks permission/error details but is sufficient for agent selection.

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?

The input schema covers both parameters with descriptions (zone_id and record_id), so schema coverage is 100%. The description adds no additional parameter detail, earning the baseline score of 3.

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?

The description clearly states 'Permanently delete a DNS record' with a specific verb and resource, distinguishing it from sibling tools like create, update, get, and list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly instructs to 'Use list_dns_records first to confirm the record ID', providing a clear prerequisite and workflow context. It doesn't mention alternatives for when not to use, but for a destructive operation this is solid.

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

Deploy Server