Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Create dns record

cloudflare_create_dns_record
Destructive

Create a DNS record in a Cloudflare zone, setting type, name, content, TTL, and proxy status to route traffic or connect external hosts.

Instructions

[UNIFIED] Create a DNS record (DNS:Edit permission). For a proxied A/AAAA record set proxied=true; for CNAME to another host keep proxied=false when the target is outside Cloudflare, or true when both sides are proxied. TTL 1 means automatic.

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": {
      "site": "<site>",
      "zone_id": "<zone_id>",
      "type": "<type>",
      "name": "<name>",
      "content": "<content>"
    },
    "name": "cloudflare_create_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNo
nameYes
siteYes
typeYes
commentNo
contentYes
proxiedNo
zone_idYes
priorityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds the auth requirement (DNS:Edit permission), which is genuine value, but says nothing about duplicate-name behavior, overwrite risk, or that repeats create additional records despite the tool being destructive.

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?

Three tight sentences with the permission requirement front-loaded and the per-type proxied rule immediately after. Dense but every clause carries information; only the redundant '[UNIFIED]' tag and repeated proxied phrasing could be trimmed.

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 9-parameter, non-idempotent, destructive mutation with no output schema and 0% schema description coverage, the description documents only two parameters and omits record-type semantics, required-field meaning, and error behavior. An agent could still call it, but with substantial guesswork on seven fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% with 9 parameters, so the description must carry the full documentation burden. It explains only proxied (conditionally) and ttl (1 = automatic), leaving site vs zone_id, type, name, content, comment, and priority completely undefined in both schema and description.

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 and resource ('Create a DNS record') plus the required API permission (DNS:Edit), which lets an agent separate it from cloudflare_update_dns_record, cloudflare_delete_dns_record, and the list/get siblings. The '[UNIFIED]' prefix is unexplained noise but doesn't obscure the purpose.

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 gives conditional guidance on proxied for A/AAAA vs CNAME and explains TTL=1, which is real operational guidance. However, it never says when to choose this tool over the sibling update tool (e.g., modifying an existing record) or what preconditions exist beyond the permission.

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

Deploy Server

Other Tools