Skip to main content
Glama
oborseth

Official Porkbun MCP Server

by oborseth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Nameservers

update_nameservers
DestructiveIdempotent

Replace the complete nameserver set for a domain in your Porkbun account, overwriting any existing entries. Use dry_run to validate the change before it is applied.

Instructions

Replace the nameservers for a domain in the authenticated account. This is a full replacement, not an append — the supplied list becomes the complete set of nameservers. Most TLDs require 2-13 entries. Setting custom nameservers disables Porkbun's free DNS hosting for the domain. Idempotent: applying the same NS list twice is a no-op. The list is applied as a set — the registry may return it in a different order, so do not expect get_nameservers to echo your ordering back, and do not treat a reordering as drift.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to update, e.g. `example.com`
dry_runNoIf true, validate only — returns wouldSucceed without changing the nameservers.
nameserversYesFull list of nameservers (e.g. `['ns1.example.com', 'ns2.example.com']`). Minimum 2, maximum 13.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.39.4
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "If true, validate only — returns wouldSucceed without changing the nameservers.",
+  "type": "boolean"
+}
  2. First observedv0.4.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations cover destructive/idempotent hints, but the description adds material behavioral context beyond them: disabling Porkbun free DNS hosting (a real side effect), the TLD 2-13 constraint, idempotency semantics, and the ordering caveat warning that a reordered registry response is not drift. This is exactly the kind of context annotations cannot carry.

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?

Front-loaded with the core action, then the caveats that matter. Every sentence (replacement semantics, TLD range, DNS hosting impact, idempotency, ordering) carries distinct information; none is 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?

For a destructive, no-output-schema mutation tool with full schema coverage, the description supplies everything an agent needs: replacement semantics, side effects, idempotency, and the ordering expectation. Nothing material is missing.

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% (baseline 3), and the description adds genuine meaning on top: it explains the nameservers list is applied as a complete set and unordered, which the schema's min/max bounds alone do not convey. dry_run semantics remain schema-only.

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: 'Replace the nameservers for a domain in the authenticated account.' The 'full replacement, not an append' clause immediately distinguishes it from any additive NS operation, and get_nameservers is implicitly the read counterpart.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly frames when to use it: full-set replacement, not append. It does not explicitly name sibling alternatives (e.g. 'use get_nameservers to inspect first'), leaving routing to inference, but the semantic guidance is strong.

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