Skip to main content
Glama

Connect custom domain

set_domain
Idempotent

Connect a custom domain the user owns to an HTML page of format html or a site, without a password. Needs a profile token, or an owner token added to a free BrewPage profile (up to 5 domains). Returns the DNS records for the user to create exactly as returned.

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": {
      "type": "<type>",
      "namespace": "<namespace>",
      "id": "<id>",
      "hostname": "<hostname>"
    },
    "name": "set_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
typeYes
hostnameYesBare hostname: www.example.com
namespaceYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / hostname / description
      Previous value: -"Bare hostname the user owns: www.example.com or example.com, no scheme or path"New value: +"Bare hostname: www.example.com"
    • removedInput schema / properties / id / description
      Removed value: -"Publication ID"
    • removedInput schema / properties / namespace / description
      Removed value: -"Publication namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"A profile token, or the publication's owner token added to a BrewPage profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / type / description
      Removed value: -"Publication type"
  2. Changed2 schema fields changed
    • changedInput schema / properties / hostname / description
      Previous value: -"Domain or subdomain the user owns, e.g. www.example.com or example.com"New value: +"Bare hostname the user owns: www.example.com or example.com, no scheme or path"
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token in a BrewPage profile: the publication's own token added to the profile, or a profile token. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"A profile token, or the publication's owner token added to a BrewPage profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare this is a non-read-only, idempotent, non-destructive mutation, and the description adds real value beyond that: the no-password constraint, the authentication requirement, the 5-domain cap on free profiles, and the fact that DNS records are returned for the user to create verbatim. It omits what happens if the hostname is already connected, which is the main remaining gap.

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?

Two dense sentences with the action, target, and auth front-loaded and nothing gratuitous. The phrasing 'an HTML page of format html or a site' is slightly awkward but still parseable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter mutation with 20% schema coverage and no output schema, the description covers purpose, auth, quota, and return behavior well, but leaves two of five parameters undocumented and does not explain the id/namespace relationship. It is adequate but not complete for the tool's complexity.

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 only 20% across 5 parameters, so the description must carry weight, and it does partially: it explains type ('html or a site'), implies hostname via 'custom domain', and maps 'profile token, or an owner token' to ownerToken. The id and namespace parameters remain entirely unexplained in both schema and description, leaving the page-identification pair opaque.

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 definition states a specific verb and resource — connect a custom domain the user owns — and scopes it to an HTML page of type html or a site. That is enough for an agent to distinguish it from check_domain, remove_domain, and list_domains without opening another schema, though no sibling is named explicitly.

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 clear usage context: the domain must belong to the user, the target must be an html page or site, and authentication is via a profile token or an owner token on a free BrewPage profile. It does not state exclusions (e.g., when to use check_domain first, or what to do for an already-connected domain), so it stops short of full when/when-not guidance.

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.