MCP Cloudflare DNS Server

import_dns_zone

Import DNS records from a JSON array into a Cloudflare zone. Creates each record and returns a success/failure summary, with partial failures handled individually.

Instructions

Import DNS records from a JSON array, creating each record in the zone. Returns a success/failure summary with partial failure handling.

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": {
      "records": "<records>"
    },
    "name": "import_dns_zone"
  }
}

Input Schema

Name	Required	Description	Default
`records`	Yes	Array of DNS record objects to create
`zone_id`	No	Cloudflare zone ID. Omit to use CLOUDFLARE_ZONE_ID env var.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 30, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does add a valuable trait: returns a success/failure summary with partial failure handling, implying non-atomic behavior. However, it does not disclose duplicate handling, whether imports are additive, batch limits, or authentication/zone requirements beyond what the schema states.

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 action and scope, and no filler or repetition. The outcome is stated compactly.

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?

The description covers the core operation and return style (summary with partial failures), but no output schema exists, and the description omits details such as duplicate behavior, idempotency, import limits, or how to target a zone (though the schema mentions the env var fallback). This is adequate but leaves several operational questions open.

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%, so the schema already documents records and zone_id. The description adds no parameter-level detail beyond 'JSON array', which is already reflected in 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 states a specific verb ('Import') and resource ('DNS records from a JSON array, creating each record in the zone'), making the batch-create purpose unambiguous. It also contrasts with sibling create_dns_record (single record) and export_dns_zone (opposite direction).

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

Usage Guidelines3/5

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

The description implies batch import usage through 'from a JSON array' and 'each record', but it never explicitly says when to choose this over create_dns_record or when not to use it. No exclusions or alternative tool names are provided.

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

Deploy Server