Skip to main content
Glama

List custom domains

list_domains
Read-only

Read custom domains without a DNS check: status, problem, DNS records. No address: every domain of the profile (admin profile token).

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": "list_domains"
  }
}

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: -"Whole list or by hostname: an admin profile token. By publication: a profile token or an owner token added to the profile. 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. Changed5 schema fields changed
    • addedInput schema / properties / hostname
      Added value: +{
      +  "description": "Custom domain as a bare hostname, e.g. www.example.com; instead of type, namespace and id",
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Publication ID",
      +  "type": "string"
      +}
    • addedInput schema / properties / namespace
      Added value: +{
      +  "description": "Publication namespace",
      +  "type": "string"
      +}
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Admin token of the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"Whole list or by hostname: an admin profile token. By publication: a profile token or an owner token added to the profile. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Publication type; with namespace and id, instead of hostname",
      +  "enum": [
      +    "html",
      +    "site"
      +  ],
      +  "type": "string"
      +}
  3. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds meaningful behavior beyond that: it says no DNS check occurs, identifies status, problem, and DNS records as returned content, and indicates scope by profile/admin token. Pagination and exact auth requirements are still omitted.

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 definition is very short, front-loaded, and free of filler. The 'No address:' fragment is awkward and slightly reduces clarity, but the overall structure is efficient.

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

Completeness2/5

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

For a tool with five optional parameters, zero required parameters, low schema coverage, and no output schema, the description should explain how filters like type, hostname, namespace, and ownerToken affect results. It partially covers return fields but leaves most parameter behavior and scope selection unclear.

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%, with hostname the sole documented parameter. The description does not explain id, type, namespace, or ownerToken semantics, and the cryptic phrase 'No address' does not map clearly to any of them, so it fails to compensate for the low coverage.

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 description clearly states that the tool reads custom domains and explicitly avoids a DNS check, which distinguishes it from check_domain. The second sentence about scope (every domain of the profile, admin profile token) is less clear but still supports the listing purpose.

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?

The phrase 'without a DNS check' implies a contrast with check_domain, but the description never explicitly says when to use this tool versus that sibling or any other listing/filtering alternative. Usage is implied rather than stated.

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.