Skip to main content
Glama

Remove custom domain

remove_domain
Destructive

Remove a custom domain from the profile; the BrewPage link keeps working.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "remove_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
typeNo
hostnameNoInstead of type, namespace and id
namespaceNo
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: -"Custom domain as a bare hostname, e.g. www.example.com; instead of type, namespace and id"New value: +"Instead of type, namespace and id"
    • 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: -"By publication: a profile token or an owner token added to the profile. By hostname: an admin profile token. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / type / description
      Removed value: -"Publication type; with namespace and id, instead of hostname"
  2. Changed2 schema fields changed
    • changedInput schema / properties / hostname / description
      Previous value: -"Custom domain, e.g. www.example.com; instead of type, namespace and id"New value: +"Custom domain as a bare hostname, e.g. www.example.com; instead of type, namespace and id"
    • changedInput schema / properties / ownerToken / description
      Previous value: -"By publication: an owner token in the profile. By hostname: an admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"By publication: a profile token or an owner token added to the profile. By hostname: an admin profile token. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  3. Added

TDQS

B3.4/5.0
Behavior3/5

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

The destructive annotation already flags this as a mutation, and the description adds one genuinely non-obvious fact: the underlying BrewPage link survives the removal. It does not say whether DNS records are left orphaned, whether the operation is reversible, or that an owner token/authorization is required — relevant gaps for a destructive tool.

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?

A single front-loaded sentence with a secondary clause that carries real information (the link keeps working); nothing redundant or padded.

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, zero-required-parameter tool, the description covers the core action and the main post-condition. What's missing is addressing-mode guidance for the five loosely coupled parameters, which matters less given the schema exposes them, but still leaves the agent to figure out id/type versus hostname on its own.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% across five parameters, and the description compensates for none of them. It gives no hint about the id/type vs hostname/namespace addressing alternatives, the html/site enum, or the ownerToken, all of which an agent must infer from bare schema fields.

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?

States a specific verb and resource: 'Remove a custom domain from the profile.' An agent can distinguish it from set_domain or check_domain, though it never explicitly names the inverse/alternative tools to reinforce the distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the operation itself plus the assurance that the BrewPage link keeps working, which hints at 'use this to drop a custom hostname without unpublishing.' There is no explicit when-to-use, when-not-to-use, or pointer to set_domain/check_domain as alternatives.

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.