Skip to main content
Glama
oborseth

Porkbun MCP Server

by oborseth
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

list_domains

Read-onlyIdempotent

List domains from your Porkbun account with optional filters and sorting. Returns up to 1000 domains per page with metadata such as expire date, auto-renew, and API access status.

Instructions

List domains in the authenticated Porkbun account. Returns one page (up to 1000) with metadata: expire date, auto-renew, security lock, WHOIS privacy, API access opt-in, and notLocal flag.

Filters (all optional):

  • domain: exact match. Returns 0 or 1.

  • name_contains: substring search on domain name.

  • tlds: limit to these TLDs (no leading dot).

  • expiring_within_days: only domains expiring within N days. Useful for renewal automation.

  • auto_renew: 'yes' or 'no'.

  • api_access: 'yes' or 'no'. Filter to domains an API key can actually operate on — eliminates API_ACCESS_DISABLED errors downstream.

  • sort_name: 'domain' | 'tld' | 'create_date' | 'expire_date'. Default expire_date.

  • sort_direction: 'asc' | 'desc'. Default asc.

For a single domain by name, use get_domain instead — cleaner shape and 404-on-not-found semantics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoExact domain match — returns 0 or 1 result.
name_containsNoCase-insensitive substring on the full domain name.
tldsNoLimit to these TLDs (no leading dot). Example: ['com', 'io']
expiring_within_daysNoOnly domains expiring within this many days from now.
auto_renewNoFilter to domains with auto-renew on or off.
api_accessNoFilter to domains opted in to API access.
sort_nameNoSort field.
sort_directionNoSort direction.
startNoPagination offset. Default 0.
include_labelsNoInclude user-defined domain labels in the response.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint; description adds transparency about pagination (up to 1000 per page), return metadata fields, and filter semantics. No contradiction with annotations, which already cover read-only 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?

Well-structured with a clear opening sentence and a bulleted list of filters. While slightly lengthy, every sentence adds meaning and avoids redundancy.

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?

Despite no output schema, the description comprehensively covers return metadata, pagination limits, and all 10 parameters with optional filters. Differentiates from sibling tool and addresses common use cases adequately.

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?

Input schema covers 100% of parameters with descriptions. The description adds contextual value beyond schema, such as noting that api_access filter eliminates downstream errors and that expiring_within_days is useful for renewal automation.

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 lists domains in the authenticated Porkbun account, specifies return metadata (expire date, auto-renew, etc.), and distinguishes from the sibling tool get_domain for single-domain lookup.

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?

Provides explicit guidance on when to use this tool vs. get_domain for single domains, and explains each filter's purpose (e.g., api_access prevents errors). Does not explicitly compare to all siblings but offers sufficient context for common use cases like renewal automation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oborseth/Porkbun-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server