mcp-cloudflare-crunchtools

Create Dns Record Tool

create_dns_record_tool

Create a new Cloudflare DNS record by specifying zone, type, name, and content, with optional TTL, proxy, priority, and comment settings.

Instructions

Create a new 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": {
      "zone_id": "<zone_id>",
      "type": "<type>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "create_dns_record_tool"
  }
}

Input Schema

Name	Required	Description
`ttl`	No	TTL in seconds, 1 = auto (default: 1)
`name`	Yes	Record name (e.g., www, @, subdomain.example.com)
`type`	Yes	Record type (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA)
`comment`	No	Optional comment
`content`	Yes	Record content (IP address, target domain, etc.)
`proxied`	No	Proxy through Cloudflare (default: false)
`zone_id`	Yes	Zone ID (32-character hex string)
`priority`	No	Priority for MX/SRV records

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.7.2Oct 12, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / comment / description
```
Added value: +"Optional comment"
```
- addedInput schema / properties / content / description
```
Added value: +"Record content (IP address, target domain, etc.)"
```
- addedInput schema / properties / name / description
```
Added value: +"Record name (e.g., www, @, subdomain.example.com)"
```
- addedInput schema / properties / priority / description
```
Added value: +"Priority for MX/SRV records"
```
- addedInput schema / properties / proxied / description
```
Added value: +"Proxy through Cloudflare (default: false)"
```
- addedInput schema / properties / ttl / description
```
Added value: +"TTL in seconds, 1 = auto (default: 1)"
```
- addedInput schema / properties / type / description
```
Added value: +"Record type (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA)"
```
- addedInput schema / properties / zone_id / description
```
Added value: +"Zone ID (32-character hex string)"
```
Changed9 schema fields changedv0.5.1Oct 1, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / comment / description
```
Removed value: -"Optional comment"
```
- removedInput schema / properties / content / description
```
Removed value: -"Record content (IP address, target domain, etc.)"
```
- removedInput schema / properties / name / description
```
Removed value: -"Record name (e.g., www, @, subdomain.example.com)"
```
- removedInput schema / properties / priority / description
```
Removed value: -"Priority for MX/SRV records"
```
- removedInput schema / properties / proxied / description
```
Removed value: -"Proxy through Cloudflare (default: false)"
```
- removedInput schema / properties / ttl / description
```
Removed value: -"TTL in seconds, 1 = auto (default: 1)"
```
- removedInput schema / properties / type / description
```
Removed value: -"Record type (A, AAAA, CNAME, MX, TXT, NS, SRV, CAA)"
```
- removedInput schema / properties / zone_id / description
```
Removed value: -"Zone ID (32-character hex string)"
```
First observedv0.5.0Aug 19, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does almost none of it. It does not state required permissions, whether the record is created immediately, idempotency, or error conditions for invalid zone/type combinations.

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

Conciseness3/5

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

A single front-loaded sentence with no waste, so structure is fine. Its brevity, however, reflects under-specification rather than disciplined concision, keeping it at minimum-viable.

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?

For a mutation tool with 8 parameters and no annotations, the description is inadequate. An output schema exists so return values need not be explained, but the absence of any usage, permission, or behavioral context leaves the definition incomplete.

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%, documenting all 8 parameters (ttl, name, type, content, proxied, priority, zone_id, comment), so the schema already does the heavy lifting. The description adds zero parameter meaning, which sets it at the baseline of 3 under the coverage rule.

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?

States a specific verb (Create) and resource (DNS record), so an agent immediately knows the operation. However, it offers no differentiation from siblings like update_dns_record_tool, delete_dns_record_tool, or create_page_rule_tool, which is the key remaining gap at this level.

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 on when to use this tool versus update_dns_record_tool or list_dns_records_tool, no prerequisites, and no stated context. The agent must infer usage entirely from the name.

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

Deploy Server