cloudflare-mcp-pro

delete_dns_record

DestructiveIdempotent

Deletes a DNS record by its ID. Requires human approval to execute; without it, returns a preview of the deletion.

Instructions

Delete a DNS record by ID. Requires confirm:true (human-approval gate); without it returns a preview only.

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
`zone_id`	Yes	The Cloudflare zone ID (32-char hex). Get it from list_zones.
`record_id`	Yes	DNS record ID to delete.
`confirm`	No	Human-approval gate: must be true to actually perform this mutating operation. Omit or set false to get a non-executing preview of what would happen (with secrets redacted). A human should approve before this is set to true.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already indicate destructive and idempotent behavior. The description adds value by disclosing the preview-only behavior without confirm, which is not captured in annotations. However, it does not describe what the preview contains or error cases.

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 core purpose and then the key behavioral note. No wasted words.

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

Completeness3/5

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

Given no output schema, the description should explain the preview response content. It only says 'returns a preview only' without details. Annotations partially compensate but the description could be more complete.

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 baseline is 3. The description adds minimal value beyond the schema, only restating the confirm gate. It does not explain parameter format or constraints beyond the schema descriptions.

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 'Delete a DNS record by ID', specifying the verb and resource, and distinguishes from sibling delete tools. It also mentions the unique confirm gate.

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?

Description explicitly states that confirm=true is required for actual deletion, and without it a preview is returned. This provides clear guidance on when and how to use the tool, though it could be improved by noting when to choose delete over alternatives like update.

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

Deploy Server