Skip to main content
Glama

Get an AirApp website's state

airapps_site_state
Read-only

Whether the Website engine is available here (engine), the public address, publication (not live / live / live with unpublished changes), the public switch (isPublic), the preview and live versions, currentVersion (what the files would deploy as now), previewStale (files changed since the preview), and blockers that stop the files from deploying.

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

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

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
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, so the safety profile is covered. The description adds useful context about what the fields mean (blockers that stop deployment, previewStale meaning files changed since the preview) and how reads relate to deploys. It does not cover return shape or error behavior beyond the notion of blockers.

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?

Front-loaded: the returned fields are listed first, ahead of the endpoint line and the multi-space caveat. The workflow paragraph is informative but somewhat tangential to a state read and could be trimmed without harm.

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?

No output schema exists, so the description carries the return-value burden, and it enumerates the returned concepts well enough to know what to expect. The notable gap is the required nodeId parameter, undocumented in both schema and description.

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 documented in-schema with the auth_verify guidance, while required nodeId is a bare string with no schema description. The description reinforces the targetSpaceId workflow but never explains what nodeId is or where to obtain it, leaving the required parameter under-specified.

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 specific read of a resource (the Website state of an AirApp) and enumerates the precise fields returned: engine availability, address, publication status, isPublic, versions, currentVersion, previewStale, and blockers. That field-level enumeration distinguishes it from siblings such as airapps_site_domains or airapps_site_deploy_preview.

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 concrete usage condition for multi-space accounts: call auth_verify, ask the user which space, then pass targetSpaceId. It also sketches the deploy workflow (preview, then go live) that frames where this read fits. It does not explicitly say when to prefer it over siblings like airapps_site_domains or airapps_site_republish, so not a 5.

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.