Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cloudflare: Delete dns record

cloudflare_delete_dns_record
Destructive

Delete a specified Cloudflare DNS record using its zone and record IDs. Use it to remove obsolete entries, noting that resolution stops immediately and records must be recreated if needed.

Instructions

[UNIFIED] Delete a DNS record (DNS:Edit permission). DESTRUCTIVE — the record and its resolution stop working immediately; recreate it with create_dns_record if needed.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
zone_idYes
record_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the bar is lower, but the description still adds real value: it discloses that the record and its resolution stop working immediately (consequence of the mutation) and that DNS:Edit permission is required. It does not cover idempotency or error behavior, keeping it short of a 5.

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?

Two short sentences with zero padding; the destructive consequence is front-loaded before the recovery advice, so an agent reading only the first clause gets the critical warning.

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

Completeness3/5

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

For a destructive, no-output-schema tool the description covers consequence, permission, and recovery well, but leaves all three required identifiers undocumented, which is a meaningful gap for correct invocation. Adequate but not complete.

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 description coverage is 0% for all three required parameters (site, zone_id, record_id), and the description says nothing about their meaning, format, or where to obtain them. With low coverage the description is expected to compensate, and it does not.

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 ("Delete a DNS record") and is unambiguously distinct from the get/list/update/create DNS siblings. The parenthetical permission hint and the remediation pointer to create_dns_record reinforce what this tool does and what it undoes.

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 destructive warning implies the usage context, and it names create_dns_record as the recovery path, but there is no explicit guidance on when to delete versus update, or on prerequisites beyond the (DNS:Edit permission) note. Usage is inferable rather than stated.

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