porkbun-mcp

by major

Overview Schema Source Related Servers Discussions Admin

Python

Remote

domains_delete_url_forward

Destructive

Delete a URL forwarding rule from a domain. Provide the domain and forward ID to remove the unwanted redirect.

Instructions

Delete a URL forwarding rule.

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>",
      "forward_id": "<forward_id>"
    },
    "name": "domains_delete_url_forward"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Domain name (e.g., 'example.com')
`forward_id`	Yes	URL forward ID to delete

Output Schema

Name	Required	Description	Default
`status`	Yes	Operation status
`message`	Yes	Confirmation message

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.2Aug 7, 2026

TDQS

A3.6/5.0

Behavior2/5

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

The description adds no behavioral context beyond the destructiveHint annotation. It does not disclose whether deletion is permanent, what happens to associated data, or any side effects. With the annotation already indicating destructiveness, the description offers minimal additional transparency.

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 a single, front-loaded sentence ('Delete a URL forwarding rule.') with no wasted words. It is appropriately concise for the simplicity of the tool.

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

Completeness4/5

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

For a simple delete tool with two well-documented parameters, an output schema, and a destructiveHint annotation, the one-sentence description is largely complete. However, it omits guidance on how to obtain the forward_id (e.g., from domains_get_url_forwards), which would be useful context but is not strictly required given the schema.

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 input schema provides full descriptions for both parameters ('domain' and 'forward_id'), covering 100% of the parameter semantics. The tool description does not add any additional meaning, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Delete') and resource ('URL forwarding rule'), making it immediately clear what the tool does. It also distinguishes itself from sibling tools like domains_add_url_forward and domains_get_url_forwards by naming the exact operation.

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?

The description implies usage through the verb 'Delete' but provides no explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites, such as needing to obtain the forward_id from domains_get_url_forwards, nor any exclusions or alternative tool references.

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