Skip to main content
Glama
Sign In
cPanel MCP Server

cPanel MCP Server

by 0xHayd3n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

disable_hotlink_protection

Disable hotlink protection in cPanel to allow external websites to directly link to your images and files, resolving broken links and enabling content sharing.

Instructions

Disable hotlink protection

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'Disable hotlink protection' without explaining effects, scope (e.g., domain-wide), reversibility, or prerequisites. This is a mutating operation that could have security implications, yet no such context is given.

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 a single sentence, which is short, but it is under-specified rather than genuinely concise. Every word restates the name, providing no added value. This is not effective conciseness but rather a failure to elaborate on necessary operational details.

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

Completeness1/5

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

For a mutating tool that disables a security feature, the description is completely inadequate. It does not explain what happens when hotlink protection is disabled, whether it can be re-enabled, or how it relates to sibling tools. The lack of any behavioral context makes this tool risky for an agent to invoke without further information.

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 is empty (100% coverage by default). The baseline for 0-parameter tools is 4, and the description correctly requires no parameter documentation. No additional parameter semantics are needed.

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 'Disable hotlink protection' is a near-verbatim restatement of the tool name. It states the verb and resource but adds no new information, essentially being a tautology. While it is clear, it does not distinguish itself from siblings beyond what the name already conveys.

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?

The description provides no guidance on when to use this tool versus alternatives like enable_hotlink_protection or get_hotlink_protection. There is no mention of context, prerequisites, or exclusions, leaving the agent without any basis for selecting this tool over others.

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