Skip to main content
Glama

Website: set the client's domain

website_domain

Set the domain a client's new website will go live on (www.) and get the two DNS records to add: a TXT record that proves it's theirs, and the CNAME that switches the site over at launch. Also says how to forward the bare domain to www. Agencies can instead download the pages (website_save) and host them anywhere.

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": {
      "client": "<client>",
      "domain": "<domain>"
    },
    "name": "website_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes
domainYese.g. acmefence.com or www.acmefence.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=true), so the description's job is to add context — and it does, explaining that the domain is set before go-live and that two DNS records come back plus bare-domain forwarding guidance. It doesn't address what happens if a domain is already configured or any permission/rate constraints, which is the 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, front-loaded with the primary action and the return payload, then the alternative path. Slightly overloaded by the parenthetical and the mid-sentence DNS explanation, but no sentence is filler.

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 only two required parameters and no output schema, the description carries the return-value burden well by naming both DNS records and the forwarding step. It is nearly complete for a setup-stage mutation, lacking only edge-case behavior (domain already set, impact of changing it) and clarification for the undocumented `client` parameter.

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 50%: only `domain` carries a description (an example of acmefence.com vs www.acmefence.com), while `client` is bare. The description partially compensates by clarifying that the site goes live on the www-prefixed form and the bare domain is forwarded, which explains the accepted domain format, but it never says what `client` should contain (ID, name, or slug).

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 — 'Set the domain a client's new website will go live on' — and goes further by declaring what the call yields: a TXT verification record and the CNAME that switches the site at launch. That output detail distinguishes it from website_domain_check (verification) and website_launch (switch-over) without the agent needing to open other schemas.

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?

Gives a clear context ('a client's new website') and names an explicit alternative with its condition: agencies can download pages via website_save and host anywhere. It stops short of stating when to prefer website_domain_check or when to move on to website_launch, so the sibling routing within the launch workflow is only implied.

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.