Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_email_account

Remove an email account from your cPanel hosting by specifying the full email address. Permanently delete the mailbox and associated settings.

Instructions

Delete an email account

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": {
      "email": "<email>"
    },
    "name": "delete_email_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to delete (user@domain.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without warning that deletion is likely irreversible, mentioning data loss, or describing what happens to associated resources like forwarders or autoresponders.

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 declarative sentence with absolutely no wasted words. It is concise and straightforward, matching the simplicity of the tool.

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?

Despite having a simple schema and fully described parameter, the tool is destructive and lacks annotations or an output schema. The description omits critical context about side effects, irreversibility, or post-deletion status, making it incomplete for safe agent operation.

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 fully describes the only parameter 'email' with format 'user@domain.com', so schema coverage is 100%. The description itself adds no parameter-specific information, warranting the baseline score of 3.

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 'Delete an email account' clearly states a specific verb and resource, making it unambiguous. It is distinguishable from sibling delete tools (e.g., delete_email_forwarder, delete_postgresql_database) by resource type, though it does not explicitly contrast with them.

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, prerequisites, or consequences. The description merely states the action without contextualizing it among related email account tools like create_email_account or change_email_password.

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