porkbun-mcp-server

create_dnssec_record

Publish a DNSSEC DS record at the registrar by specifying key tag, algorithm, digest type, digest, and audit reason. Optionally add key data for DNSKEY-derived records.

Instructions

Publish a DNSSEC DS record at the registrar. Required: key_tag, alg, digest_type, digest. Optional key_data_* fields apply only when you're also publishing the DNSKEY-derived form. reason is required and tags the audit row as action=DNSSEC_ADD.

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": "<domain>",
      "key_tag": "<key_tag>",
      "alg": "<alg>",
      "digest_type": "<digest_type>",
      "digest": "<digest>",
      "reason": "<reason>"
    },
    "name": "create_dnssec_record"
  }
}

Input Schema

Name	Required	Description	Default
`alg`	Yes
`digest`	Yes
`domain`	Yes
`reason`	Yes
`key_tag`	Yes
`digest_type`	Yes
`max_sig_life`	No
`key_data_flags`	No
`key_data_pub_key`	No
`key_data_protocol`	No
`key_data_algorithm`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so the description carries full burden. It explains the audit tagging with reason and the optional nature of key_data_* fields, but lacks details on side effects, authorization requirements, or error handling.

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 sentences, front-loaded with the core action, no redundant information. Every sentence adds value.

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?

With 11 parameters, 6 required, no output schema, and no annotations, the description provides a basic understanding of the tool's purpose and parameter roles but lacks details on return values, error conditions, or postconditions, making it only moderately complete.

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 0%, so description must compensate. It identifies required parameters (key_tag, alg, digest_type, digest) and explains reason's audit role, and that key_data_* fields are only relevant for DNSKEY-derived form. However, it does not explain parameter formats or valid values, leaving gaps for 11 parameters.

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 clearly states the verb 'Publish' and the specific resource 'DNSSEC DS record at the registrar', distinguishing it from sibling tools like delete_dnssec_record and create_dns_record.

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 description lists required parameters and mentions optional fields apply only for DNSKEY-derived form, providing some context. However, it does not explicitly state when to use this tool versus alternatives or provide conditions for use.

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

Deploy Server