Skip to main content
Glama

Publish the previewed version (Go live)

airapps_site_go_live
Destructive

Puts the previewed version on the public address, and only that version. outcome: preview-stale means the files changed after the preview, so nothing was published: deploy the preview again first. outcome: no-preview means there is no preview yet. Anyone with the address can use a public site.

POST /api/v1/airapps/{nodeId}/site/go-live

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. Go live only when the user asks. Anyone with the address can use a public site, with the access level its airapp.json asks for: tell the user the address and that level first. preview-stale means the files changed after the preview: deploy the preview again, never publish unseen files another way.

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_go_live"
  }
}

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

A4.6/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description discloses meaningful behavior: the two outcome signals (preview-stale, no-preview) and their remedies, the fact that the site becomes publicly usable by anyone with the address, and the requirement to tell the user the address and access level before going live. It also notes that record changes need no redeploy, which is non-obvious.

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?

Front-loaded and generally efficient, but the preview-stale explanation appears twice (opening paragraph and closing sentence) and the 'anyone with the address can use a public site' warning is likewise repeated, adding redundancy without new information.

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 mutation tool with no output schema, the description covers sequencing, prerequisites, failure outcomes, and the public-exposure consequence, which is most of what an agent needs. It stops short of describing the full response payload beyond the outcome field, but the critical decision-relevant behavior is present.

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

Parameters4/5

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

Schema coverage is 50%: targetSpaceId is already documented in the schema, but the description adds the workflow around it (call auth_verify first, ask the user, then pass it). nodeId is only implied by the POST path, so there is still a small gap for the required parameter.

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?

First sentence gives a specific verb and resource plus a scoping constraint: it publishes the previewed version, and only that version, to the public address. This clearly distinguishes it from the preview deploy, and the stale/no-preview outcome explanations reinforce the boundary between previewing and publishing.

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

Usage Guidelines5/5

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

Explicit when-to-use guidance: 'Go live only when the user asks,' plus the prerequisite sequence (deploy the members-only preview after file changes, then go live) and the negative case ('never publish unseen files another way'). It also states the multi-space prerequisite of calling auth_verify and asking the user.

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.