@kodim/mcp-cloudflare-dns

Import DNS Records

import_dns_records

Import DNS records from BIND zone file content to create new records in Cloudflare.

Instructions

Import DNS records from BIND-formatted zone file content. Creates new records from the provided content.

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

Input Schema

Name	Required	Description
`proxied`	No	Whether imported records should be proxied through Cloudflare
`zone_id`	Yes	The zone ID
`bind_content`	Yes	BIND zone file content to import

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations mark readOnlyHint=false, consistent with a write operation. The description adds that it 'creates new records', clarifying the mutation type, but does not disclose potential side effects like record conflicts, replacement behavior, or failure conditions.

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, 22 words, front-loaded with 'Import DNS records'. Every sentence adds value without 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?

The tool has no output schema, yet the description does not mention return values or error scenarios. It covers the core action and input format adequately but could benefit from noting response behavior or idempotency, especially since it is a bulk mutation.

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 coverage is 100% with descriptions for all three parameters (zone_id, bind_content, proxied). The description's mention of 'BIND-formatted zone file content' reinforces the bind_content parameter but adds no further meaning beyond the schema.

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 the specific verb 'Import' with the resource 'DNS records' and uniquely specifies the source format 'BIND-formatted zone file content', distinguishing it from sibling tools like create_dns_record and batch_dns_records.

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 clearly indicates the intended input type ('BIND-formatted zone file content') and states the action ('Creates new records'), signaling a bulk import scenario. However, it does not explicitly mention alternatives or exclusions.

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

Deploy Server