Skip to main content
Glama

Delete Cloudflare DNS record

delete_cloudflare_dns_record
Destructive

Delete a DNS record from one of the organisation's Cloudflare domains. The record belongs to the customer and lives in their own Cloudflare account: Ankra cannot restore it, and removing a record that live traffic depends on takes the hostname down immediately. Always read the record with list_cloudflare_dns_records and show the user exactly which record (name, type and content) will be removed before calling. Deleting a record Ankra did not create (managed_by 'external') is especially worth confirming - something outside Ankra put it there.

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>"
    },
    "name": "delete_cloudflare_dns_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.3/5.0
Behavior3/5

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

The description provides important behavioral context beyond annotations: Ankra cannot restore deleted records, live traffic can be taken down immediately, and external records warrant confirmation. However, the annotations already declare destructiveHint=true and readOnlyHint=false, so the description's incremental value, while useful, mostly reinforces and expands on known destructive behavior.

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?

The description is front-loaded with the destructive consequence, then the prerequisite verification step, then the external-record edge case. Every sentence adds useful decision or safety context for an irreversible action.

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 tool with annotations and full schema coverage, the description supplies the missing operational context: no restoration, live-traffic impact, required pre-call verification, and external-record caution. Nothing essential for safe invocation appears absent.

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 coverage is 100%, so the schema already documents domain_id, record_id, and credential_name. The description does not add meaningful syntax or format details beyond advising how to identify the record to delete.

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 states a specific verb and resource: deleting a DNS record from one of the organisation's Cloudflare domains. It also clarifies ownership and account context, making it clearly distinct from create/update/list DNS record siblings.

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?

It explicitly requires reading the record with list_cloudflare_dns_records and showing the user the exact record before calling. It also highlights the special confirmation case for records marked managed_by 'external'.

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.