Skip to main content
Glama

Turn the public address back on

airapps_site_republish

Serves the version that was already live again after an unpublish. Publishes nothing new; outcome: no-preview means nothing has ever gone live.

POST /api/v1/airapps/{nodeId}/site/republish

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

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

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-destructive write in a closed world, so the bar is lower. The description adds real context beyond them: that this is a write that allocates no new version, that a `no-preview` outcome means nothing was ever live, and that multi-space accounts require asking the user which space to target.

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 core behavior is front-loaded in the first sentence, with the edge-case outcome immediately after. The HTTP route line and the trailing lifecycle paragraph are useful but make the block feel like three loosely joined fragments rather than one structured statement.

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 carries the return-signal burden and does so by explaining the `no-preview` outcome. It also covers the auth prerequisite for multi-space accounts. What is missing is guidance on what nodeId refers to and what the agent should do after a successful republish.

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 merely echoed here, while nodeId is the required parameter the schema leaves bare. The endpoint template `{nodeId}/site/republish` reveals that nodeId is a path identifier for the AirApp, but it does not explain how to obtain one, so the description only partly compensates.

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?

"Serves the version that was already live again after an unpublish. Publishes nothing new" states a specific verb and the exact scope of the action, and the negation cleanly separates it from a fresh publish. It never names airapps_site_go_live or airapps_site_deploy_preview directly, so an agent must infer the boundary from the lifecycle sentence rather than from an explicit comparison.

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

Usage Guidelines4/5

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

The trigger condition is explicit: use this after an unpublish to restore what was previously public. The lifecycle note (deploy members-only preview, then go live, and record changes need no redeploy) tells the agent when this step is or is not part of the flow. It could be sharper about what to call instead when nothing has ever been live, but `outcome: no-preview` signals that state.

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.