cPanel MCP Server

delete_addon_domain

Remove an addon domain and its associated subdomain from cPanel hosting, freeing up resources and eliminating unwanted domain configurations.

Instructions

Delete an addon domain

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>",
      "subdomain": "<subdomain>"
    },
    "name": "delete_addon_domain"
  }
}

Input Schema

Name	Required	Description	Default
`domain`	Yes	Addon domain to remove
`subdomain`	Yes	Associated subdomain

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 6, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, and the description adds no behavioral context beyond the operation name. It does not disclose the destructive nature explicitly, whether it cascades to the associated subdomain, or any permission requirements. For a delete operation, this is a significant gap.

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 short sentence with no filler. It is front-loaded and appropriately sized for such a simple operation. Every word earns its place, and it avoids any unnecessary detail.

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?

Given the simplicity of the delete operation and complete schema coverage, the description is minimally adequate. However, it lacks any context about what happens to the associated subdomain, error behavior, or prerequisites, making it incomplete for an agent that needs to make safe decisions.

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 describes both parameters with complete coverage, so the baseline is 3. The description itself adds no additional meaning beyond the schema's parameter descriptions. Since coverage is 100%, it meets the baseline but does not exceed it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Delete' and the resource 'addon domain'. It is unambiguous and aligns with the tool name, though it does not explicitly differentiate it from sibling operations like create_addon_domain or list_addon_domains. The verb itself distinguishes it, but some additional context could be added.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, restrictions, or references to sibling tools. An agent must infer usage solely from the name and description, which offers no contextual steering.

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

Deploy Server