MCP Cloudflare DNS Server

get_dns_record

Retrieve a specific DNS record by its ID from a Cloudflare zone. Get exact record details when you need to inspect or verify a single entry.

Instructions

Get a specific DNS record by ID

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

Input Schema

Name	Required	Description	Default
`zone_id`	No	Cloudflare zone ID. Omit to use CLOUDFLARE_ZONE_ID env var.
`recordId`	Yes	The DNS record ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.4Aug 30, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description must carry the behavioral disclosure burden. 'Get' signals a read-only retrieval operation with no mutation, which is useful, but the description does not disclose error behavior, missing-record handling, or what fields are returned. It is minimally transparent but lacks behavioral depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, tightly worded sentence with no filler and the core operation front-loaded. It is appropriately concise for a simple getter, though it does not attempt to add any additional guidance.

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?

For a simple 2-parameter getter the description is mostly adequate, but the absence of an output schema and any annotations leaves the return shape and error behavior unspecified. The description tells the agent what the tool does but not enough about what the agent should expect back.

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 both 'zone_id' and 'recordId' already documented, including the 'CLOUDFLARE_ZONE_ID' fallback for 'zone_id'. The description itself adds no parameter-level meaning, so it stays at the schema-driven baseline.

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 'Get' and identifies the resource as 'a specific DNS record by ID', clearly distinguishing it from 'list_dns_records' and other sibling operations. An agent can immediately understand the tool's scope and that it targets a single record rather than a collection.

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 phrase 'specific ... by ID' implies that this tool is for fetching a known single record, but it does not explicitly state when to use this tool versus 'list_dns_records' or when to avoid it. The usage context is present but only implied, not explicitly routed against alternatives.

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

Deploy Server