Skip to main content
Glama

Replace the ENTIRE DNS zone (destructive)

replace_all_dns_records
Destructive

Replace a domain's entire DNS record set with the exact records you provide, permanently deleting any existing records not included. Requires explicit confirmation; fetch current records first for rollback.

Instructions

DANGER: overwrite the domain's complete record set with exactly the records you provide. Every existing record NOT in your list is permanently deleted, MX mail records included. Prefer modify_dns_records for everyday edits. Requires confirm=true; an empty record set additionally requires allowEmptyZone=true. Consider calling get_dns_records first to capture the current zone for rollback.

On Route 53 the zone's own SOA and apex NS are left alone regardless — Route 53 creates both with the hosted zone and rejects deleting either.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
confirmNoMust be true to perform the destructive replace.
recordsYesThe COMPLETE desired record set. Anything omitted is deleted.
providerNoForce a provider instead of routing by domain. Needed when the domain does not exist yet (registration), and useful when a domain is at two providers and you mean a specific one.
allowEmptyZoneNoRequired true to submit an empty record set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYes
failedYes
accountYes
appliedYes
successYes
providerYes
environmentNo
recordCountYes
nonAtomicWarningNo
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses permanent deletion of omitted records including MX, requires confirm=true and allowEmptyZone=true for empty zones, and explains Route 53's SOA/apex NS behavior. This adds rich behavioral context beyond what annotations provide.

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 tight paragraphs with a front-loaded 'DANGER' warning. Every sentence contributes critical safety, usage, or provider-specific information with no fluff.

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?

Covers purpose, destructive semantics, prerequisites, rollback advice, alternatives, and provider-specific exception. With an output schema present, return values need not be explained.

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 high (80%), so baseline is 3. The description adds value by clarifying the records array is the complete desired set ('Anything omitted is deleted') and explicitly tying confirm/allowEmptyZone to the destructive behavior, plus the provider parameter for force-routing.

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 uses specific verb 'replace' with resource 'entire DNS zone', explicitly stating every record not in the list is permanently deleted. It clearly distinguishes from sibling modify_dns_records by naming it as the alternative for everyday edits.

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?

Explicitly directs users to prefer modify_dns_records for everyday edits, and recommends calling get_dns_records first for rollback. This provides clear when-to-use vs. alternative guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fledgeling-co/namecheap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server