porkbun-mcp-server

create_dns_record

Create a DNS record on a domain with a required audit reason. Returns success and the new record ID.

Instructions

Create a DNS record on domain. name is the subdomain ("" for apex). reason is required and goes into the audit row. Returns {"status": "SUCCESS", "id": <int>} on success.

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

Input Schema

Name	Required	Description	Default
`ttl`	No
`name`	Yes
`prio`	No
`type`	Yes
`notes`	No
`domain`	Yes
`reason`	Yes
`content`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 8, 2026

TDQS

C2.9/5.0

Behavior3/5

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

The description discloses the return format and that `reason` goes into the audit row, providing some behavioral context. However, it does not mention authentication needs, error handling, idempotency, or consequences of duplicate records. With no annotations, the description carries the full burden and is insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences and front-loads the core action. It uses formatting (backticks) for parameter references. However, given the parameter count, it could be slightly more structured without being verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, 5 required, and no output schema or annotations, the description is incomplete. It does not cover error conditions, validation rules, or behavior for different record types. The return format is given but user expectations for many inputs remain unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains `domain`, `name`, and `reason`, but omits details for `type`, `content`, `ttl`, `prio`, and `notes`. For instance, it does not describe valid values for `type` or how `content` varies by type, leaving significant gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Create a DNS record on `domain`'), the resource, and mentions key parameters. However, it does not explicitly differentiate from siblings like bulk_create_dns_records or create_dnssec_record, which could cause ambiguity.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as bulk_create_dns_records or create_dnssec_record. The description only states that `reason` is required for audit, but lacks context on appropriate usage scenarios or limitations.

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

Deploy Server