porkbun-mcp-server

bulk_create_dns_records

Create multiple DNS records on a domain, reporting successes and failures for each entry.

Instructions

Create multiple DNS records on domain. Porkbun has no native bulk endpoint — this fans out one create per record with continue-and-report semantics: failures collect in failed, successes in created. Each entry needs type / name / content; ttl / prio / notes are optional. reason is required and tags every per-record audit row.

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>",
      "records": "<records>",
      "reason": "<reason>"
    },
    "name": "bulk_create_dns_records"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes
`reason`	Yes
`records`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It clearly discloses the 'continue-and-report' semantics, failure collection in 'failed', success in 'created', and per-record audit tagging via 'reason'. This is strong but lacks details on potential side effects like rate limits.

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 succinct with two sentences, covering purpose, behavior, and parameter guidance. While effective, it uses backticks for emphasis and could be more structurally formal, but remains efficient.

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

Completeness4/5

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

Given no output schema, the description implies the return structure (failed, created arrays) and explains the fan-out behavior and audit tagging. It does not explicitly describe the output format, but the inference is clear. The domain parameter is self-explanatory.

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

Parameters5/5

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

The schema coverage is 0%, so the description is the sole source of parameter meaning. It explicitly lists required fields (type, name, content) and optional ones (ttl, prio, notes) for each record, and explains that 'reason' is required and tags audit rows. This fully compensates for the vague schema.

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 specifies 'Create multiple DNS records' on a domain, contrasting with single-record sibling tools. It explicitly states that Porkbun lacks a native bulk endpoint, clarifying the tool's purpose as a fan-out workaround.

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?

The description implies when to use this tool (for bulk operations) and mentions the fan-out semantics. While it does not explicitly name alternatives, the sibling context (e.g., create_dns_record) and the description's mention of 'no native bulk endpoint' provide implicit guidance.

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

Deploy Server