Skip to main content
Glama

List a website's custom domains

airapps_site_domains
Read-only

Each bound domain's fresh status (pending, active, error), the DNS records to add (dnsRecords), this deployment's findings as codes (issues) and the provider's own messages (errors), plus the CNAME target (cnameTarget) a new domain should point to. Checks again on every call.

GET /api/v1/airapps/{nodeId}/site/domains

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. An AirApp's website: after its files change, deploy the members-only preview, then go live to put that same version on the public address. Changes to records need no redeploy.

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": {
      "nodeId": "<nodeId>"
    },
    "name": "airapps_site_domains"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeIdYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, and the description adds a genuinely useful trait: "Checks again on every call," i.e. no caching, results are live DNS status. It also notes record changes need no redeploy, clarifying side effects. It stops short of stating permissions or what happens when a domain is in the error state.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence is an unfront-loaded enumeration of return fields before the reader knows what the tool does as a whole, and the closing deploy-preview/go-live narrative is largely about sibling tools' sequencing. The content is dense and useful but the ordering weakens scanability.

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 no output schema, the description properly compensates by naming the return fields (status values, dnsRecords, issues, errors, cnameTarget) and their meaning, which is exactly what an agent needs to interpret results. Gaps remain on what nodeId identifies and whether results are grouped by domain.

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%: targetSpaceId is fully documented in the schema and the description reinforces it with the auth_verify procedure, but nodeId has no schema description and no explanation here either. Baseline 3 is right given the description only compensates for one of the two parameters.

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 enumerates the specific payload of the tool (bound domains, dnsRecords, issues, errors, cnameTarget) and gives the underlying GET /api/v1/airapps/{nodeId}/site/domains path, so the resource is unmistakable. The verb is implicit rather than stated ("Each bound domain's ..." + "Checks again on every call"), and the closest siblings (bind/unbind_domain) are never named as the alternatives this read-only listing contrasts with.

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?

It gives a concrete prerequisite for multi-space accounts (call auth_verify, ask the user which space, pass targetSpaceId) and places the tool in a deploy-preview-then-go-live workflow. However, it never explicitly says when to call this versus airapps_site_state or the bind/unbind siblings, and the workflow sentence mostly describes other tools' jobs.

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.