MCP Cloudflare DNS Server

delete_dns_record

Delete a DNS record by its ID to remove stale or incorrect entries from your Cloudflare DNS zone.

Instructions

Delete a DNS record

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

Input Schema

Name	Required	Description	Default
`zone_id`	No	Cloudflare zone ID. Omit to use CLOUDFLARE_ZONE_ID env var.
`recordId`	Yes	The DNS record ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only that a record is deleted, but does not mention that deletion is destructive or irreversible, any permission requirements, or what happens after deletion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise and front-loaded, with no redundant words. It is appropriately short for a simple tool, though it contributes little beyond restating the operation implied by the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive tool with no annotations and no output schema, the description is incomplete. It does not explain the destructive consequence, how the optional zone_id interacts with the required recordId, or what a successful deletion returns.

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%, so the parameters are already fully documented in the schema. The description itself adds no parameter-level meaning, which is acceptable given the high schema coverage.

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 uses a specific verb ('Delete') and a clear resource ('a DNS record'), which unambiguously distinguishes it from sibling tools like create_dns_record, update_dns_record, and get_dns_record. An agent can immediately determine the tool's core function.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no mention of how it relates to sibling operations. The agent is left to infer from the tool name alone.

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

Deploy Server