Skip to main content
Glama

Get Publish Status

get_publish_status
Read-only

Read-only publish snapshot for a project: published (true/false, with the live URL when published), customDomains (the user's own domains attached to the project — apex and www are listed separately; empty when none), paid (the workspace owner has a paid plan, which allows removing the Floot badge), plan (free | pro | power — paid cannot tell Pro from Power), nativeBuilds (the owner's remaining monthly iOS/Android app-build allowance; unlimited is true on plans where the ceiling is only a fair-use backstop, and while an Action Boost is live (boostUntil says until when; builds started before then never count toward the allowance) — read this BEFORE passing mobile: true, and on a metered plan build only when the user asked for a native/TestFlight/Play build), displayFlootLogo (whether the live app shows the 'Made with Floot' badge; true until a paid owner turns it off), and mobileBuild (the project's latest native app build: building, succeeded, or failed with what to fix; on a succeeded build, storeBuilds says how each store's build and upload went (building, live, or failed), which can fail after the native build succeeded; isMobileTestMode marks a mobile test build — an app build finishes minutes AFTER the publish job it rode on, so read this to learn how it ended before telling the user it worked). This is the ONLY tool that reports attached custom domains — read it before telling a user whether their domain is connected, and never conclude a domain is unattached from any other output. The publish card calls this on load to render fresh state; also check it before publishing to know whether publish_app will publish fresh or publish the live app again.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_publish_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 still adds genuinely new behavioral context: the data is a live snapshot, custom-domain truth exists only here, metered build allowance semantics, and the timing caveat that a native build completes minutes after the publish job. What it omits is failure behavior (e.g., what a not-yet-published or unauthorized project returns).

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 with the one-line purpose before the field-by-field breakdown, and with no output schema the return-value enumeration genuinely earns its space. It is a single dense paragraph with heavy parenthetical nesting, which hurts scannability, but there is essentially no filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because there is no output schema, the description carries the full burden of documenting return values and does so field by field, including edge cases like `paid` not distinguishing Pro from Power and `storeBuilds` failing after a successful native build. An agent has everything needed to interpret the response and to decide when to call it.

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 0% and the description never explains projectId — whether it is a slug, UUID, or the currently open project. With a single obvious required identifier the gap is minor, so this sits at the minimum-viable baseline rather than being penalized heavily.

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?

Opens with a precise verb+resource framing ('Read-only publish snapshot for a project') and then enumerates exactly what the snapshot contains (published, customDomains, paid, plan, nativeBuilds, displayFlootLogo, mobileBuild). It actively differentiates itself from siblings: it claims exclusivity ('This is the ONLY tool that reports attached custom domains') and contrasts itself with publish_app's behavior.

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?

Gives explicit when-to-use triggers and even when-not-to-conclude rules: read before telling a user their domain is connected, never infer attachment from other outputs, read before passing mobile: true, and check before publishing to learn whether publish_app will publish fresh or re-publish. These are concrete routing rules an agent can act on without opening any other definition.

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.

Resources