Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Restore DNS Zone

restore_dns_zone
Destructive

Restore a domain's DNS zone to a saved restore point. By default, add back missing records without removing newer ones; use prune to delete extras.

Instructions

Put a domain's DNS zone back to a saved restore point. Call diff_dns_restore_point first and show the user what will change.

By default this only ADDS BACK what is missing. It does not remove records added since — pass prune: true for that, and only after reading the extra list, because 'restore my records' usually means 'put back what I lost', not 'delete everything I have done since'.

The restore is itself reversible. The zone's state from immediately before is saved and returned as previousStateSavedAs; restore that id to undo. Use dry_run: true to rehearse — it reports exactly what would change and changes nothing.

Read failed in the response. Parking records and other masked types (ALIAS, HTTPS) are managed by another part of the platform and cannot be recreated this way; they appear in failed rather than being counted, so restored is always a true number. If a parking record is what is missing, the domain needs re-parking on the website instead. SOA and NS are never touched.

A restore only matters if this zone is the one being served. If the domain is delegated to another provider, the response carries a warnings string saying so: the records went back, and nothing the user can see has changed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pruneNoAlso DELETE live records that are not in the restore point. Default false. Destructive — confirm with the user first.
domainYesDomain to restore, e.g. `example.com`
dry_runNoIf true, report what would change without changing anything.
snapshot_idYesRestore point id from `list_dns_restore_points`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.39.4

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds far more: the default non-destructive add-back-only semantics, that prune deletes live records, that the restore is itself reversible via previousStateSavedAs, the `failed` semantics for masked record types, the delegation warning, and that SOA/NS are never touched.

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?

Long but front-loaded and sectioned with bold lead-ins; each paragraph carries a distinct operational fact (default behavior, reversibility, failure modes, delegation caveat) with no filler.

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?

With no output schema, the description supplies the return-value semantics an agent needs (restored, failed, previousStateSavedAs, warnings) and covers the destructive/permission-adjacent caveats, leaving no significant gap for a tool of this complexity.

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 goes beyond the schema by explaining what prune actually does to live records and when it is safe to set, and by framing dry_run as a rehearsal that reports what would change.

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 ('Put a domain's DNS zone back to a saved restore point') and immediately routes the agent to the sibling diff_dns_restore_point. It is clearly distinguishable from list_dns_restore_points and the create/update/delete_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?

Explicit precondition ('Call diff_dns_restore_point first and show the user what will change') and explicit conditional guidance for the alternative behavior (pass prune: true only after reading the `extra` list). It also names dry_run as the rehearsal path.

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