porkbun-mcp-server

add_label

Create and attach a colored label to a domain for organization, with each label requiring a reason for auditable traceability.

Instructions

Create a Porkbun label and attach it to domain. color is a Porkbun-defined color name (orange, red, blue, ...). Returns {"status": "SUCCESS", "id": <int>}. action=LABEL_ADD.

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>",
      "label_name": "<label_name>",
      "color": "<color>",
      "reason": "<reason>"
    },
    "name": "add_label"
  }
}

Input Schema

Name	Required	Description	Default
`color`	Yes
`domain`	Yes
`reason`	Yes
`label_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jul 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Returns example JSON format, but lacks details on side effects (e.g., overwriting labels), permissions, or limits. No annotations to compensate.

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?

Two sentences plus action note; concise but action note feels redundant. Front-loaded with key purpose.

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

Completeness3/5

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

Adequate for simple tool with 4 required params; explains purpose and return value, but not all parameters or potential issues.

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?

Schema coverage 0%, description explains color (with examples) and domain, but leaves label_name and reason unexplained.

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?

Clear statement: 'Create a Porkbun label and attach it to domain.' Verb (create) and resource (label) are specific, and distinguishes from siblings like list_labels and remove_label.

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?

No explicit when-to-use or alternatives. The description implies it's for adding labels, but doesn't contrast with remove_label or other domain operations.

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

Deploy Server