Skip to main content
Glama

Connect a custom domain

connect_domain
Destructive

Connects a domain the owner already owns (for example www.joesplumbing.com.au) to a site. Returns the DNS records the owner must add at their domain provider: a CNAME and an ownership TXT record (the domain does not go live without the TXT). It usually goes live within minutes to a few hours after the DNS change. If the records are still not found after 7 days, the domain is removed and can be connected again. Requires a plan with custom domains. Bare domains are not supported: connect the www version and redirect the bare domain to it at the domain provider. Once the records are added, check_domain reports whether the domain is live.

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": {
      "site_id": "<site_id>",
      "hostname": "<hostname>"
    },
    "name": "connect_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site id from list_sites or create_site.
hostnameYesThe domain to connect, for example www.joesplumbing.com.au. Use a www or other subdomain, not a bare domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by explaining the two-record DNS payload, that the domain will not go live without the TXT record, propagation timing, and the 7-day auto-removal consequence (which is the practical meaning of destructiveHint=true). It does not state auth requirements or whether reconnecting reuses the same ownership token, so it stops short of a 5.

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?

Leads with what the tool does and what it returns, then layers constraints, timing, and the follow-up tool in descending priority. No filler sentences; each one adds an operational fact.

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, the description supplies the return value (CNAME plus ownership TXT), the failure lifecycle (7-day removal, reconnectable), the bare-domain workaround, and the verification tool. An agent has everything needed to call it and tell the user what to do next.

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 100% and both parameters already document the www-example and the bare-domain restriction, so the description largely repeats the schema. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

States a specific verb and resource ('Connects a domain ... to a site') and immediately describes the output ('Returns the DNS records the owner must add ... a CNAME and an ownership TXT record'), which distinguishes it cleanly from check_domain and disconnect_domain.

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?

Gives explicit prerequisites (a plan with custom domains), an explicit constraint ('Bare domains are not supported: connect the www version and redirect the bare domain'), and routes the agent to the correct follow-up tool ('Once the records are added, check_domain reports whether the domain is live').

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.

Resources