mcp-server-cloudflare

cf_dns_delete

Remove DNS records from Cloudflare by specifying zone and record IDs to manage domain configurations.

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

Input Schema

Name	Required	Description	Default
`zoneId`	Yes	Zone ID
`recordId`	Yes	DNS record ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Mar 10, 2026

TDQS

C2.9/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 full burden. 'Delete' implies a destructive mutation, but it doesn't disclose critical behaviors: whether deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure. This is a significant gap for a destructive tool with zero annotation coverage.

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?

The description is a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration.

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?

Given this is a destructive tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., permanence, permissions), usage guidelines, and output expectations, making it inadequate for safe and effective use by an AI agent.

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%, with clear parameter descriptions (zoneId, recordId). The description doesn't add any meaning beyond the schema, such as how to obtain these IDs or their format. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a DNS record' clearly states the action (delete) and resource (DNS record). It distinguishes from siblings like cf_dns_create (create) and cf_dns_list (list), but doesn't specify Cloudflare context or differentiate from other delete tools like cf_kv_delete or cf_worker_delete.

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing zoneId and recordId from cf_dns_list), exclusions, or comparisons with sibling tools like cf_dns_create for updates or cf_cache_purge for related operations.

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

Deploy Server