Cactal

Rename the platform subdomain

websiteDomains_renamePlatformDomain

Destructive

Moves the website to <label>.<platform domain>, the free address every website is allocated at creation. label is just the leading part: 1-40 characters, lowercase letters, digits, and inner hyphens, and it may not be one of the labels Cactal reserves. The change takes effect immediately, on published and draft hosts alike. The previous hostname is released at the same moment, with no redirect and no grace period, so any existing links to it break and another website may claim it. Take care on a published site. Fails with 409 when the label is already taken by another website; renaming to the label the website already has is a no-op. Custom domains are unaffected, and if one of them is primary it stays the canonical address.

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": {
      "websiteId": "<websiteId>",
      "label": "<label>"
    },
    "name": "websiteDomains_renamePlatformDomain"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes
`websiteId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the destructive/openWorld annotations, the description discloses the exact consequences: immediate effect on published and draft hosts, the previous hostname released with no redirect or grace period so existing links break and can be claimed by another site, 409 on label collision, and no-op semantics for same-label renames. This is precisely the operational detail the annotations cannot convey.

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 result of the call is front-loaded, followed by label constraints, timing, destruction consequences, and failure modes in a tight sequence. Dense but every sentence carries distinct operational information; nothing is redundant.

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

Completeness5/5

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

With no output schema and no annotations covering side effects, the description supplies everything an agent needs: what changes, when it takes effect, what is destroyed, conflict and no-op behavior, and the interaction with primary custom domains. Nothing material is missing.

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?

Schema description coverage is 0%, so the description must carry the load — and it does for `label`: 1-40 characters, lowercase letters, digits, inner hyphens, and exclusion of Cactal-reserved labels, which goes well beyond the bare `minLength: 1` in the schema. `websiteId` is only implied by 'Moves the website', leaving a small gap.

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 states a specific verb and resource — moving the website to `<label>.<platform domain>` — and frames it as the free address every site gets at creation, which cleanly separates it from the custom-domain siblings (createCustomDomain, setPrimaryDomain, removeCustomDomain). An agent can identify the tool's effect without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: the tool changes the free platform hostname, custom domains are unaffected, and renaming to the existing label is a no-op. The caution 'Take care on a published site' signals risk without explicitly stating when not to use it or naming a sibling alternative for related domain work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Cactal tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?