Skip to main content
Glama
Sign In
obambu-cpanel-mcp

obambu-cpanel-mcp

by RodrigueDev13
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_email

Delete an email account from a cPanel domain by providing the local part and domain. Permanently removes the mailbox.

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>",
      "domain": "<domain>"
    },
    "name": "delete_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesLocal part of the address to delete
domainYesDomain of the mailbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description must convey behavioral risks. It only says 'delete' without disclosing that deletion is permanent, whether associated data is removed, or if special permissions are required. For a destructive operation, this is a significant transparency gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, focused sentence with no filler or redundancy. It is concise and front-loaded, though it could add more detail without becoming verbose.

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?

For a destructive tool with no annotations, the description is too thin. It does not mention return behavior, side effects, permanence, or any operational caveats. Given the simplicity of the tool, a bit more behavioral context would make it complete.

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 has 100% description coverage for both parameters (email and domain), so the schema does the heavy lifting. The description adds no additional meaning about parameter usage or format.

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 clear verb+resource construction ('Delete an email account') that immediately distinguishes it from siblings like create_email and list_emails. It states exactly what the tool does.

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 usage context is implied: use this when you need to remove an email account. However, there is no explicit guidance about prerequisites, alternatives, or when not to use it.

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