@kodim/mcp-cloudflare-dns

Export DNS Records

export_dns_records

Read-only

Export all DNS records for a zone in BIND format to back up or migrate to another DNS provider.

Instructions

Export all DNS records for a zone in BIND format. Useful for backups or migrating to another DNS provider.

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>"
    },
    "name": "export_dns_records"
  }
}

Input Schema

Name	Required	Description	Default
`zone_id`	Yes	The zone ID

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?

The annotation readOnlyHint: true already indicates a safe read operation. The description adds meaningful behavioral details: it exports 'all DNS records' and outputs in 'BIND format', which goes beyond the annotation. No contradiction exists.

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 concise sentences that each add value: the first states what the tool does, the second states when to use it. No fluff or redundancy.

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?

For a simple export tool with one parameter, a read-only annotation, and no output schema, the description covers the essential context: purpose, output format, and use case. It could mention the response format (e.g., text output) but the BIND format implies it adequately. Overall, it is sufficiently 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?

The input schema describes zone_id as 'The zone ID' with 100% coverage. The description does not add additional parameter semantics, but the schema is fully self-explanatory, so a baseline of 3 is appropriate.

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 the specific verb 'export' applied to 'all DNS records for a zone' and specifies the output format 'BIND format'. This distinguishes it from sibling tools like list_dns_records (list) or get_dns_record (single record).

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?

The description gives clear usage context: 'Useful for backups or migrating to another DNS provider.' While it doesn't explicitly name alternatives or exclusions, the purpose is clearly identified, and the context is sufficient for an agent to decide when to use this tool.

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

Deploy Server