Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_domains

List all domains on a cPanel account, covering main, addon, sub, and parked domains. Use this to retrieve domain details for monitoring and management.

Instructions

List all domains on the account (main, addon, sub, parked)

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": "list_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description must convey the behavioral profile. It clearly states the scope (all domains on the account) and enumerates the types included. However, it does not disclose the return format, pagination, or any potential operational nuances, so it only partially carries the burden.

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 sentence of minimal length that front-loads the action and resource. Every word adds value, and there is no filler or redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (no parameters, no output schema, no annotations), the description is mostly complete. It specifies the exact scope and types of domains covered. The main gap is the absence of any detail about the returned data structure, but for a simple list operation this is a minor omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema has no properties, meaning the schema description coverage is effectively complete. With no parameters to explain, the description does not need to add parameter-level detail. Per the rubric, a baseline of 4 is appropriate.

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 specific verb ('List') and clearly identifies the resource ('all domains on the account') with an explicit enumeration of domain types (main, addon, sub, parked). This distinguishes it from sibling tools like list_subdomains, list_addon_domains, and list_parked_domains by covering all types at once.

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 implies that this tool should be used when you need all domain types together, but it does not explicitly state when to prefer this over the more specific sibling tools or provide any exclusionary guidance. No alternatives are named.

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