vibedeploy

Detach a custom domain

remove_custom_domain

DestructiveIdempotent

Remove a custom domain from a site. The site itself is unaffected; only the custom hostname is detached. The {name}.vibedeploy.be subdomain keeps serving the site.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	No	The custom domain to remove (e.g. 'tester.subsite.site'). Provide this OR recordId.
`recordId`	No	The recordId returned by add_custom_domain. Provide this OR domain.
`siteName`	Yes	The site to detach the domain from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`domain`	Yes
`removed`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

removedOutput schema / properties / request_id

Removed value: -{
-  "description": "Server-assigned request correlation id. Quote it when contacting support.",
-  "type": "string"
-}

Changed1 schema field changedJul 20, 2026

addedOutput schema / properties / request_id

Added value: +{
+  "description": "Server-assigned request correlation id. Quote it when contacting support.",
+  "type": "string"
+}

First observedJun 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate destructive and non-read-only behavior. The description adds valuable scoping context beyond the annotations: the site is not destroyed, only the custom hostname is detached, and the default subdomain remains active. This meaningfully clarifies the blast radius of the operation.

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 three short sentences with no filler. It front-loads the primary action, then clarifies scope, then notes the fallback service behavior. Every sentence contributes useful decision-relevant information.

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?

For a destructive but narrowly scoped operation, the description is complete: it states what is removed, what remains unaffected, and which service continues to serve the site. The schema handles parameter specifics and the output schema covers return values, so nothing essential is missing.

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 documentation covers all three parameters with clear descriptions, including the domain-or-recordId choice. The description adds no parameter-specific details beyond the schema, so with 100% schema coverage the baseline of 3 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 clearly states the action: removing a custom domain from a site, with the effect scoped to only the custom hostname. The title 'Detach a custom domain' reinforces the resource and operation, and the scope notes distinguish it from site deletion and from add/verify/list domain operations.

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?

The description gives clear usage context by explaining that the site itself is unaffected and that the fallback subdomain keeps serving. This helps the agent use the tool for detaching a hostname rather than deleting the site, though it does not explicitly name alternative tools or exclusion conditions.

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

All vibedeploy tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.