Skip to main content
Glama

Add a custom domain to a website

airapps_site_bind_domain

Binds a hostname the space owns (shop.company.com, no scheme or path) to a website that has gone live, and returns the domains with the DNS records to add at the DNS provider. The domain serves the site once DNS and HTTPS are ready.

POST /api/v1/airapps/{nodeId}/site/domains

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. Add a domain only when the user asks; give them the returned dnsRecords to add at their DNS provider, then check again with the domain list.

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_bind_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

A4.5/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds real context on top: the site must already be live, the call returns DNS records for the user to apply, and the domain serves traffic only after DNS and HTTPS are ready. It stops short of saying what happens if the hostname is already bound or already owned by another site, which is the one behavioral gap for a mutation.

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

Conciseness4/5

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

The core action is front-loaded in one dense, useful sentence. The trailing paragraph mixes multi-space auth, the deploy/go-live workflow, and DNS follow-up into one long block, so it reads as stitched-together notes rather than ordered guidance, though each note is relevant.

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?

With no output schema, the description correctly compensates by naming what is returned (domains plus dnsRecords) and what the user must do with it. Preconditions, space scoping, and the follow-up check are all covered; only error/already-bound behavior is left out.

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 coverage is only 33%, so the description has to carry weight, and it does for hostname by explaining the exact expected shape (bare host, no scheme or path) beyond the regex. targetSpaceId is reinforced with the auth_verify-then-ask workflow. nodeId is never explained in prose — only implied by the POST path template — which keeps this from a 5.

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 first sentence gives a specific verb and resource (binds a hostname to a live website) and states what comes back (domains with DNS records). It also pins the hostname format with an example (`shop.company.com`, no scheme or path), so an agent can distinguish it from the unbind and domain-list siblings 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 Guidelines5/5

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

Explicit when-to-use ('Add a domain only when the user asks'), explicit precondition (the website must have gone live), and explicit follow-through (hand the returned dnsRecords to the user, then re-check with the domain list). It also names the alternative path — deploy preview, go live, and notes record changes need no redeploy — and routes multi-space accounts through auth_verify.

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.