cpanel_delete_email
Delete an email account on your cPanel server to manage email addresses and free up resources.
Instructions
Delete an email account
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email address to delete |
Delete an email account on your cPanel server to manage email addresses and free up resources.
Delete an email account
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | Email address to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and the description fails to disclose behavioral traits such as permanence of deletion, required permissions, or whether the email account must exist.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short but not tautological; however, it could be more informative without adding much length.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simplicity of the tool (1 parameter, no output schema), the description is minimal but still lacks details on return behavior or side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the description of the parameter 'email' (Email address to delete) adds no extra meaning beyond the schema itself. Baseline score of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it deletes an email account, which is a specific verb+resource pair. It distinguishes from sibling tools like cpanel_create_email or cpanel_list_email_accounts.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like cpanel_delete_database or cpanel_delete_file. No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/aandersen2323/cpanel-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server