Skip to main content
Glama

Remove a custom domain from a website

airapps_site_unbind_domain
Destructive

The hostname stops serving this website; its generated address keeps working. Possible after a plan lapses.

DELETE /api/v1/airapps/{nodeId}/site/domains/{hostname}

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. An AirApp's website: after its files change, deploy the members-only preview, then go live to put that same version on the public address. Changes to records need no redeploy. Take a site or a domain down only when the user asks.

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": {
      "nodeId": "<nodeId>",
      "hostname": "<hostname>"
    },
    "name": "airapps_site_unbind_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
hostnameYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, so the key safety signal is structured; the description adds what is actually destroyed versus preserved ('its generated address keeps working'), which is genuinely useful scoping for a destructive call. It also discloses the auth/space-selection prerequisite. It does not cover failure modes (e.g., hostname not bound) or whether re-binding is possible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is well front-loaded and carries the core effect. However, the middle block about deploying a members-only preview and going live is workflow guidance for a different tool (deploy/publish), not for unbinding a domain, and it dilutes the focus of an otherwise short definition.

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?

For a destructive 3-parameter tool with no output schema, the definition covers the effect, the preserved state, a precondition, and the multi-space auth flow — enough to call it correctly. The remaining gap is the undocumented nodeId semantics and no mention of error behavior when the hostname is not currently bound.

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 coverage is only 33% — targetSpaceId is documented in the schema itself, and nodeId and hostname have no descriptions there. The description partially compensates by showing both in the endpoint path and explaining that 'the hostname' is the thing that stops serving, but nodeId's meaning (the site/node identifier) is never stated in prose.

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 states a specific verb and resource ('The hostname stops serving this website') and names the exact REST endpoint DELETE /api/v1/airapps/{nodeId}/site/domains/{hostname}, so there is no ambiguity about the operation. It stops short of naming the inverse sibling airapps_site_bind_domain, but the effect is specific enough that an agent can distinguish it from deploy/go-live/publish tools.

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?

It gives an explicit gating condition ('Take a site or a domain down only when the user asks') and a prerequisite path for multi-space accounts (call auth_verify, ask the user which space, pass targetSpaceId). The 'Possible after a plan lapses' note clarifies a legitimate trigger. It lacks an explicit contrast with airapps_site_unpublish or bind_domain, which would have made it a 5.

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.