Porkbun MCP Server

get_dns_records

Retrieve DNS records for a domain. Get a single record by ID or all records at once.

Instructions

Retrieves DNS records for a domain. If record_id is provided, retrieves a single record; otherwise, retrieves all records.

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>"
    },
    "name": "get_dns_records"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	The domain name.
`record_id`	No	Optional: The ID of a specific record to retrieve.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral transparency burden. It discloses the conditional behavior (single vs. all) but does not mention potential pagination, rate limits, or permissions. For a simple read operation, this is adequate but not rich.

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 concise sentences, front-loaded with the core action. No unnecessary words or repetition. Each sentence earns its place.

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 simple tool with two parameters and no output schema, the description is complete. It clearly explains the two retrieval modes and leaves no ambiguity about the tool's behavior.

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% with both parameters described. The description adds meaningful conditional logic linking record_id to the retrieval mode, going beyond the schema's static field descriptions.

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?

Description clearly states 'Retrieves DNS records for a domain' with a specific verb and resource, and further clarifies the scope: single record vs. all records based on record_id. This distinguishes it from siblings like get_dnssec_records and retrieve_dns_record_by_name_type.

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 usage: use for retrieving all records or a single record by ID. However, it does not explicitly mention alternatives or when not to use this tool, such as using retrieve_dns_record_by_name_type for name/type lookups.

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