Skip to main content
Glama

Update Cloudflare DNS record

update_cloudflare_dns_record
Destructive

Change what an existing DNS record points at. Only the fields you pass change: an omitted ttl, proxied, priority or comment keeps the record's current value, so a TTL change does not need you to restate the proxy setting. A record's name and type cannot be changed: delete it and create a new one instead. This rewrites live DNS in the customer's own account, so read the record with list_cloudflare_dns_records and confirm the new value with the user first.

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>",
      "record_id": "<record_id>",
      "content": "<content>"
    },
    "name": "update_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.
commentNoOptional comment stored on the record. Defaults to 'Managed by Ankra'.
contentYesThe record's new value.
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_idYesCloudflare record id. Discover it with list_cloudflare_dns_records.
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.8/5.0
Behavior5/5

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

Annotations only supply destructiveHint=true and idempotentHint=false; the description goes well beyond them by disclosing merge/PATCH semantics (omitted ttl, proxied, priority, comment retain current values), the immutability of name and type, and the fact that this rewrites live DNS in the customer's own account. The confirmation ritual and the pre-read requirement are behavioral context unavailable anywhere else in the definition.

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?

Four sentences, front-loaded with the core action before the merge rule, the immutability rule, and the safety ritual. Nothing is redundant, though the TTL/proxy example sentence is slightly long and could be folded into the merge rule.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema and rich (100%) parameter documentation, the description covers everything material: partial-update behavior, immutable fields, live-account impact, and the required pre-read plus user confirmation. Type-specific constraints (MX priority, proxy eligibility) are already handled by the schema.

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 baseline is 3, but the description adds real meaning by stating that omitted optional fields preserve their current values rather than clearing them -- a merge semantic the schema does not express. Minor friction: the ttl schema says 'Omit for automatic' while the description says an omitted ttl 'keeps the record's current value', two different implied defaults for the same omission.

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?

Opens with a specific verb+resource+scope: 'Change what an existing DNS record points at.' The word 'existing' separates it from create_cloudflare_dns_record, and the explicit 'delete it and create a new one instead' routes the agent to the delete/create siblings when name or type must change.

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 both when-to-use and when-not: partial field updates are in scope, name/type changes are explicitly out of scope with a named alternative workflow. It also states prerequisites -- read the record with list_cloudflare_dns_records and confirm the new value with the user -- which is exactly the guidance an agent needs before a live-DNS mutation.

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.