Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by aandersen2323
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cpanel_list_email_accounts

List all email accounts for a domain on a cPanel server. Optionally filter by domain name.

Instructions

List all email accounts for the domain

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cpanel_list_email_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain name (optional, lists all if not specified)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. However, it only states the operation and does not mention any behavioral traits such as authentication requirements, rate limits, or whether it is read-only. This is insufficient for a tool with no annotations.

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?

The description is a single concise sentence that is front-loaded with the core action. It wastes no words, though it could include additional context without losing conciseness.

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?

For a simple list operation with one parameter and no output schema, the description is adequate but lacks completeness regarding the output format or any special behavior. It does not leverage the sibling tools to provide context.

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?

There is one optional parameter ('domain') with 100% schema description coverage. The description does not add any semantic value beyond the schema, so it meets the baseline score of 3 as per guidelines.

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 'List all email accounts for the domain' clearly specifies a listing operation on email accounts, scoped to a domain. It effectively distinguishes from sibling tools like 'cpanel_create_email' or 'cpanel_delete_email', which are mutation operations.

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 description implicitly indicates usage for listing email accounts, but provides no explicit guidance on when to use this tool versus alternatives, nor when not to use it. Given the context of sibling tools, the usage is implied but not clarified.

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