Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by aandersen2323
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cpanel_list_subdomains

Lists all subdomains associated with the cPanel account, providing a complete overview of existing subdomains for management purposes.

Instructions

List all subdomains

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_subdomains"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description alone must disclose behavioral traits. It states 'List' implying a read-only operation, but lacks details on what exactly is listed (e.g., full subdomain names, records), authentication requirements, or any side effects.

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 with no wasted words. However, it could be slightly more informative without losing conciseness, such as adding what information is returned.

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?

Given no annotations, no output schema, and a simple listing task, the description is minimal. It does not clarify whether results include metadata like creation date or SSL status, which might be expected for subdomain management.

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 no parameters, so coverage is 100%. The description adds no parameter-level detail, but given zero parameters, the baseline score of 3 is appropriate.

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

Purpose4/5

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

The description 'List all subdomains' uses a specific verb and resource, making the tool's purpose immediately clear. It effectively distinguishes itself from sibling tools that perform different actions on subdomains (e.g., create, delete) by focusing solely on listing.

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 is provided on when to use this tool versus alternatives, such as filtering or searching. There is no mention of prerequisites, scope, or behavior differences from other list tools (e.g., cpanel_list_databases).

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