Skip to main content
Glama
oborseth

Porkbun MCP Server

by oborseth

transfer_domain

Idempotent

Initiate an inbound domain transfer to Porkbun by providing the domain, EPP code, and verified transfer cost. Returns a transfer ID for tracking progress.

Instructions

Spends account credit. Initiates a transfer of an external domain into Porkbun. Returns immediately with a transferId; the actual registry transfer takes 5-7 days for most TLDs. Use get_transfer_status to poll. Requires the auth/EPP code from the losing registrar. The cost must match the current transfer price from check_domain. .uk domains and a few TLDs do not support inbound API transfers. Idempotency-safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainYesDomain to transfer in, e.g. `example.com`
costYesTransfer price in cents. Must match the value returned by `check_domain`.
auth_codeYesAuthorization (EPP) code from the losing registrar.
Behavior5/5

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

Adds critical behavior not in annotations: spends credit, async with 5-7 day delay, cost matching requirement, TLD restrictions. No contradiction with annotations.

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?

Every sentence adds value. Front-loaded with the most important note (spends credit). Structure is clear and efficient.

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?

Covers return value (transferId), polling advice, prerequisites, restrictions, and idempotency. No output schema, but description provides sufficient context for a mutation tool.

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 descriptions cover basics, but description adds must-match constraint for cost and emphasizes auth code requirement, improving parameter understanding.

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?

Clearly states it initiates a domain transfer, spends account credit, and returns a transferId. Distinguishes from siblings like check_domain and get_transfer_status.

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

Usage Guidelines5/5

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

Explicitly says to poll with get_transfer_status, warns about TLD restrictions (.uk etc.), and specifies prerequisites (auth code, cost matching check_domain).

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