Porkbun MCP Server

create_dns_record

Add DNS records to a domain by specifying type, content, and TTL. Supports A, MX, CNAME, TXT, AAAA, and other record types.

Instructions

Adds a new DNS record to a specified domain.

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>",
      "type": "<type>",
      "content": "<content>"
    },
    "name": "create_dns_record"
  }
}

Input Schema

Name	Required	Description
`ttl`	No	Time To Live in seconds (default 600).
`name`	No	Subdomain (leave blank for root, * for wildcard).
`prio`	No	Priority (for MX/SRV records).
`type`	Yes	Record type. Valid types are: A, MX, CNAME, ALIAS, TXT, NS, AAAA, SRV, TLSA, CAA, HTTPS, SVCB.
`domain`	Yes	The domain name.
`content`	Yes	Record content/answer.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that a new DNS record is added, with no information about idempotency, validation, propagation delays, error handling, or whether duplicates are allowed. This leaves the agent without critical behavioral context.

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?

The description is a single, front-loaded sentence that directly states the action without any filler or redundant information.

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?

The tool has a simple create operation, and the schema provides rich parameter documentation. However, the description lacks guidance on expected return values, when to use this versus sibling tools, and any behavioral caveats. With no output schema and no annotations, the description is somewhat incomplete for a fully autonomous agent.

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?

All six parameters are documented with descriptions in the input schema, covering domain, type, content, ttl, name, and prio. Since schema coverage is 100%, the description does not need to repeat parameter details; baseline score of 3 applies.

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 a specific verb 'Adds' with a clear resource 'DNS record' and specifies the target 'to a specified domain'. This clearly distinguishes it from sibling tools like edit_dns_record, delete_dns_record, and get_dns_records.

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 implies the tool is used to create a new DNS record, but it does not explicitly state when to use it versus editing or deleting existing records, nor does it mention any prerequisites or alternative tools. However, the context of adding vs editing is reasonably clear.

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