Skip to main content
Glama
Sign In
porkbun-mcp-server

porkbun-mcp-server

by Avicennasis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_url_forward

Delete a URL forward from your Porkbun domain using the record ID obtained from URL forwarding list. Provide domain, record ID, and reason for removal.

Instructions

Remove a URL forward by record id (from get_url_forwarding). action=URLFWD_DELETE.

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>",
      "record_id": "<record_id>",
      "reason": "<reason>"
    },
    "name": "delete_url_forward"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
reasonYes
record_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the action (remove) and includes an internal action code, but fails to mention side effects, reversibility, permissions, or any error conditions. The destruction hint is implied but not confirmed.

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?

The description is extremely concise at two sentences, front-loading the purpose and a source hint without any fluff. Every word is necessary.

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 3 required parameters and no output schema, yet the description only covers the record_id source. It lacks details on the other two parameters, confirmation of deletion, error scenarios, and any return value, making it incomplete for safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description should compensate. It only clarifies that record_id comes from get_url_forwarding, but does not explain the meaning or format of the 'domain' or 'reason' parameters, leaving gaps in 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?

The description explicitly states 'Remove a URL forward by record id', which is a specific verb-resource combination. It also references the related tool 'get_url_forwarding' and provides the internal action identifier, clearly distinguishing it from sibling tools like delete_dns_record.

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?

The description implicitly guides usage by noting that the record_id comes from get_url_forwarding, indicating a prerequisite step. However, it does not explicitly exclude alternatives or provide when-not-to-use guidance.

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

Deploy Server

Other Tools