Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_email_forwarder

Delete an email forwarder to stop emails from being sent to an alternate address. Specify the source and destination to remove.

Instructions

Delete an email forwarder

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>",
      "forward_to": "<forward_to>"
    },
    "name": "delete_email_forwarder"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesForwarder source address
forward_toYesForwarder destination to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as permanence, authorization requirements, or side effects. The tool is destructive but this is not explicitly stated.

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

Conciseness2/5

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

The description is extremely concise but it is terse to the point of being a bare restatement of the tool name. It lacks structure and fails to convey any meaningful information beyond the name.

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 operation with no annotations and no output schema, the description is incomplete. It does not explain what happens after deletion, whether confirmation is needed, or any return behavior.

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 both parameters (source address and destination to remove) with clear descriptions, so the schema carries the burden. The tool description adds no parameter information.

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

Purpose2/5

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

The description restates the tool name verbatim ('Delete an email forwarder' = delete_email_forwarder). It provides no additional specificity about scope or behavior beyond the name itself.

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 provided on when to use this tool or how it compares to create_email_forwarder or list_email_forwarders. The description simply states the action without context.

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