domain

Call domain.records

Show what DNS a domain has and what still has to be added — 'what records do I need?', 'is the DNS set up?', 'why isn't my domain working yet?'. Show a domain's DNS: if we manage it, exactly what's in place (the records we added are marked); if we don't, the records the customer still has to add plus what the domain answers with right now. zone_held false is a normal answer, not a problem. ALWAYS relay the copy_card lines — they're written for the customer to follow. Not for whether the domain is serving yet — that is page.domain_status.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/domain.records

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/domain.records
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

domain_idstring uuid required

The domain, as a UUID. Take it from the conversation's context or from the workspace's domain list — never invent one.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 7 revisions of this API.