Skip to main content
Glama

Create Cloudflare DNS record

create_cloudflare_dns_record
Destructive

Create a DNS record in one of the organisation's Cloudflare domains. The record is written into the customer's own Cloudflare account and takes effect for real traffic, so confirm the domain and the content with the user before calling. 'name' may be a bare label (qualified against the domain), a fully-qualified name inside the domain, or '@' for the domain apex; a name outside the domain is refused. Records Ankra creates are stamped with a 'Managed by Ankra' comment. Use list_cloudflare_dns_records first to check the name is not already taken - Cloudflare refuses an exact duplicate.

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": {
      "domain_id": "<domain_id>",
      "name": "<name>",
      "record_type": "<record_type>",
      "content": "<content>"
    },
    "name": "create_cloudflare_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
ttlNoRecord TTL in seconds (60-86400), or 1 for Cloudflare's automatic TTL. Omit for automatic. A proxied record's TTL is managed by Cloudflare and must be left automatic.
nameYesRecord name: a bare label such as 'grafana', a fully-qualified name inside the domain, or '@' for the apex.
commentNoOptional comment stored on the record. Defaults to 'Managed by Ankra'.
contentYesRecord value: an IPv4 address for A, an IPv6 address for AAAA, a target hostname for CNAME, the text for TXT, the mail host for MX.
proxiedNoWhether Cloudflare's proxy (the orange cloud) fronts the record. Only A, AAAA and CNAME records can be proxied. Proxying hides the origin address and terminates TLS at Cloudflare; leave false to resolve straight to the origin.
priorityNoPriority (0-65535). Required for MX records; rejected for every other supported type.
domain_idYesCloudflare zone id of the domain. Discover ids with list_cloudflare_domains.
record_typeYesRecord type.
credential_nameNoWhich connected Cloudflare credential to use. Omit unless the organisation has several; with one connected credential Ankra resolves it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds real value beyond them by disclosing that the write lands in the customer's own Cloudflare account and affects live traffic, plus the duplicate-refusal failure mode that effectively explains non-idempotency. It stops short of saying what is returned or how partial failures surface, so it is strong but not exhaustive.

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?

Four sentences, front-loaded with the action and the live-traffic risk, then the name-qualification edge cases, then the dedupe route. No filler and no repetition of schema text beyond what carries the refusal rule.

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?

For a 9-parameter mutation tool with no output schema, the description covers the risk profile, the highest-ambiguity parameter (name), and the ordering against the list tool. The remaining gap is the response shape, since with no output schema the agent gets no hint of what a successful creation returns (for example a record id needed for later update or delete).

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds behavior the schema does not: 'name' may be a bare label, a fully-qualified in-domain name, or '@', and a name outside the domain is refused. That refusal rule is genuine semantic value beyond the field documentation; TTL, proxied, priority and credential_name are left entirely to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('Create a DNS record'), scopes it to 'one of the organisation's Cloudflare domains', and its naming plus 'Managed by Ankra' comment stamping clearly separates it from list/update/delete siblings in the same family.

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

Usage Guidelines5/5

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

Gives explicit preconditions: confirm domain and content with the user before calling, and call list_cloudflare_dns_records first to check the name is not already taken since Cloudflare refuses exact duplicates. That names both the prerequisite action and the alternative tool with the condition that selects it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.