Porkbun MCP Server

list_domains

Retrieve all domains from your Porkbun account. Use the start parameter to paginate results and include labels for additional filtering.

Instructions

Retrieves a list of domains in the Porkbun account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_domains"
  }
}

Input Schema

Name	Required	Description	Default
`start`	No	Index to start retrieving domains from (default 0).
`includeLabels`	No	Include domain labels (optional).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 7, 2026

TDQS

B3.1/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 burden of disclosing behavior. It only states 'retrieves a list' without mentioning pagination, return format, rate limits, or authentication requirements. The start and includeLabels parameters are not explained in the description, leaving the agent uncertain about the tool's full behavior.

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 a single concise sentence that clearly states the tool's purpose. It is front-loaded and free of verbosity, earning its place, though it could be slightly more detailed without becoming bloated.

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?

The tool has no output schema and no annotations, so the description must provide complete context. It lacks details on pagination, return structure, or domain fields. While the tool is simple, the description is insufficient for an agent to fully understand the response or operational constraints.

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?

The schema provides complete descriptions for both parameters (start and includeLabels), so the schema covers 100% of parameter semantics. The description adds no additional parameter information, which is acceptable per the baseline but does not enhance understanding beyond the 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 clearly states the tool retrieves a list of domains in the Porkbun account, using a specific verb and resource. It is distinct from sibling tools which focus on DNS records, pricing, SSL, and other domain-related operations.

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 is provided on when to use this tool versus alternatives. It does not mention that it lists all domains or that other tools (e.g., check_domain, get_domain_pricing) serve different purposes. No exclusions or alternative references are given.

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