Skip to main content
Glama

Take the website offline

airapps_site_unpublish
Destructive

Turns the public switch off: every website address answers not found until it is republished. Works whatever the plan, so a site can always come down.

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

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. Take a site or a domain down only when the user asks.

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

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/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, and the description adds genuinely new behavior: all addresses return not found, the state is reversible via republish, and it works on any plan. It stops short of saying whether domain bindings survive an unpublish, which matters for a destructive action.

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 effect is front-loaded well, but the trailing paragraph drifts into deploy-preview/go-live workflow and record-change advice that is not about unpublishing, and the raw 'POST /api/v1/...' line adds little for an agent.

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 two-parameter, no-output-schema destructive tool, the definition covers effect, reversibility, plan-independence, and the space-selection prerequisite. Only the persistence of domain bindings and the nodeId's meaning are left unaddressed.

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%. The multi-space/targetSpaceId guidance in the description merely restates the schema's own description, and nodeId is never explained in either place, so the description does not compensate for the coverage gap.

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?

States a concrete verb and effect: 'Turns the public switch off: every website address answers not found until it is republished.' An agent immediately knows this is the inverse of go-live/republish and what the observable result is.

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?

Gives a clear guardrail ('Take a site or a domain down only when the user asks') and rules out needless use ('Changes to records need no redeploy'). It lacks an explicit contrast with airapps_site_republish or go_live as the alternative, but the workflow sentences imply the sequence.

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.