Skip to main content
Glama

Detach a custom domain

remove_custom_domain
DestructiveIdempotent

Detach a custom domain from a site. The site itself is unaffected and keeps serving on its platform subdomain (e.g. {name}.subsite.site).

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": {
      "siteName": "<siteName>"
    },
    "name": "remove_custom_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoThe custom domain to remove, e.g. 'shop.example.com'. Provide this or recordId.
recordIdNoThe recordId returned by add_custom_domain or list_custom_domains. Provide this or domain.
siteNameYesThe site to detach the domain from.

Output Schema

NameRequiredDescriptionDefault
domainYes
removedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"The custom domain to remove (e.g. 'tester.subsite.site'). Provide this OR recordId."New value: +"The custom domain to remove, e.g. 'shop.example.com'. Provide this or recordId."
    • changedInput schema / properties / recordId / description
      Previous value: -"The recordId returned by add_custom_domain. Provide this OR domain."New value: +"The recordId returned by add_custom_domain or list_custom_domains. Provide this or domain."
  2. Changed1 schema field changed
    • removedOutput schema / properties / request_id
      Removed value: -{
      -  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / request_id
      Added value: +{
      +  "description": "Server-assigned request correlation id. Quote it when contacting support.",
      +  "type": "string"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description adds genuine value by stating that the site itself survives and continues serving on {name}.subsite.site. It does not say what happens to DNS records or verified domain state, so it is not exhaustive.

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?

Two short sentences with the action first and the consequence second; every clause carries information and nothing is padded. The parenthetical example is compact and immediately useful.

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?

An output schema exists, so return values need not be explained, and the annotations plus a 100%-covered schema carry most of the load. The one meaningful gap is post-detach side effects such as leftover DNS records or the need to re-verify, which an agent might reasonably want before calling a destructive tool.

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?

Schema description coverage is 100% and both the domain and recordId parameters already document their alternatives relationship, so the description correctly does not repeat them. It adds no syntax, format, or precedence detail beyond the schema, leaving this at the baseline.

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 uses a specific verb and resource ("detach a custom domain from a site") and clarifies the blast radius by stating the site keeps serving on its platform subdomain, which implicitly separates it from delete_site. It never names a sibling tool explicitly, so it stops short of a 5.

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?

Usage is implied by the name and by the stated outcome, but there is no explicit when-to-use or when-not-to-use guidance. It does not point the agent at list_custom_domains to find the domain or at add_custom_domain for reattaching, so the agent must infer the workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.