Skip to main content
Glama

Publish App

publish_app
Destructive

Publish the app to production: the first publish, a new publish of changes the user wants live, or a custom domain. Read get_guides('publishing') before your first call. A live app publishes at once, nothing to pass or confirm. A first publish (no domain) shows the user the publish form, and nothing publishes until they press Publish. Always publishes live (web, the mobile app when built, payments in Stripe live mode): never ask the user test or live; mobile test builds are started by the user on floot.com. If the owner has not finished Stripe setup (payments) or connected Shippo (shipping), the publish is refused with a card to do it (nothing published): tell the owner to click it, then call publish_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": "publish_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNofloot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit on a live app (it keeps its subdomain); omitted on a first publish, the user gets the publish form; on a published app a different subdomain is refused (unpublish_app first, confirming with the user). Ignored for custom_domain — the wizard collects the domain.
mobileNotrue whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, a native or mobile app, or a phone build. No store connected → a Connect card (nothing published); connected → the web app with the store builds attached. Omitted on a live app follows the saved setting on plans with unlimited app builds and means web-only on metered plans, where true spends one of a small monthly allowance (get_publish_status shows it). true / false also updates the saved setting; omitting leaves it alone.
projectIdYes
add_anotherNocustom_domain only: the user explicitly asked for an ADDITIONAL custom domain. Without it, a project that already has domains gets those domains back instead of the wizard.
domain_typeNoOmit for the floot subdomain. 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts.
include_made_with_flootNofalse removes the 'Made with Floot' badge (paid plans only — fails for free accounts). Omit to keep the current setting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit to show the user the publish form instead; on a published app a different subdomain is refused (unpublish_app first, confirming with the user). Ignored for custom_domain — the wizard collects the domain."New value: +"floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit on a live app (it keeps its subdomain); omitted on a first publish, the user gets the publish form; on a published app a different subdomain is refused (unpublish_app first, confirming with the user). Ignored for custom_domain — the wizard collects the domain."
    • changedInput schema / properties / domain_type / description
      Previous value: -"Omit for the floot subdomain (shows the publish form in the editor when domain is omitted). 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts."New value: +"Omit for the floot subdomain. 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts."
  2. Changed2 schema fields changed
    • changedInput schema / properties / add_another / description
      Previous value: -"custom_domain only: the project ALREADY has a custom domain and the user has explicitly asked for an ADDITIONAL one. Without it, a custom_domain call on a project that already has domains returns those domains instead of opening the wizard — so a user whose domain is already connected is told so rather than sent to add it again."New value: +"custom_domain only: the user explicitly asked for an ADDITIONAL custom domain. Without it, a project that already has domains gets those domains back instead of the wizard."
    • changedInput schema / properties / mobile / description
      Previous value: -"Set true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, Play Store, a native or mobile app, or a phone build — they all mean a mobile build. No store account connected → returns a Connect card (nothing published). Connected → publishes the web app with the store builds attached; the job completes when the web build is live. Omitted on a live app follows the project's saved setting: on plans with unlimited app builds that setting decides (mobile switched off stays web-only); on metered plans omitted always means web-only, and true spends one of a small monthly allowance (the remaining count comes back in the result) — read get_publish_status for the plan and allowance first. Passing true or false also updates the saved setting; omitting leaves it alone."New value: +"true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, a native or mobile app, or a phone build. No store connected → a Connect card (nothing published); connected → the web app with the store builds attached. Omitted on a live app follows the saved setting on plans with unlimited app builds and means web-only on metered plans, where true spends one of a small monthly allowance (get_publish_status shows it). true / false also updates the saved setting; omitting leaves it alone."
  3. Changed1 schema field changed
    • removedInput schema / properties / skipPaymentsOnboarding
      Removed value: -{
      -  "description": "true publishes although the owner's payments setup is unfinished; the app's payment screens stay unavailable until it is done.",
      -  "type": "boolean"
      -}
  4. Changed1 schema field changed
    • addedInput schema / properties / skipPaymentsOnboarding
      Added value: +{
      +  "description": "true publishes although the owner's payments setup is unfinished; the app's payment screens stay unavailable until it is done.",
      +  "type": "boolean"
      +}
  5. Changed3 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Ignored for custom_domain — the wizard collects the domain."New value: +"floot_subdomain only: subdomain label (lowercase, digits, hyphens, max 40). Omit to show the user the publish form instead; on a published app a different subdomain is refused (unpublish_app first, confirming with the user). Ignored for custom_domain — the wizard collects the domain."
    • changedInput schema / properties / domain_type / description
      Previous value: -"Omit to show the publish form (unpublished) or current status (published). 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts."New value: +"Omit for the floot subdomain (shows the publish form in the editor when domain is omitted). 'custom_domain' for domain setup — a paid-plan feature (get_publish_status reports `paid`); it fails for free accounts."
    • changedInput schema / properties / mobile / description
      Previous value: -"Set true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, Play Store, a native or mobile app, or a phone build — they all mean a mobile build. No store account connected → returns a Connect card (nothing published). Connected → publishes the web app with the store builds attached; the job completes when the web build is live. Omit only for a web publish."New value: +"Set true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, Play Store, a native or mobile app, or a phone build — they all mean a mobile build. No store account connected → returns a Connect card (nothing published). Connected → publishes the web app with the store builds attached; the job completes when the web build is live. Omitted on a live app follows the project's saved setting: on plans with unlimited app builds that setting decides (mobile switched off stays web-only); on metered plans omitted always means web-only, and true spends one of a small monthly allowance (the remaining count comes back in the result) — read get_publish_status for the plan and allowance first. Passing true or false also updates the saved setting; omitting leaves it alone."
  6. Changed1 schema field changed
    • addedInput schema / properties / mobile
      Added value: +{
      +  "description": "Set true whenever the request mentions iOS, Android, TestFlight, App Store, Google Play, Play Store, a native or mobile app, or a phone build — they all mean a mobile build. No store account connected → returns a Connect card (nothing published). Connected → publishes the web app with the store builds attached; the job completes when the web build is live. Omit only for a web publish.",
      +  "type": "boolean"
      +}
  7. Changed1 schema field changed
    • addedInput schema / properties / add_another
      Added value: +{
      +  "description": "custom_domain only: the project ALREADY has a custom domain and the user has explicitly asked for an ADDITIONAL one. Without it, a custom_domain call on a project that already has domains returns those domains instead of opening the wizard — so a user whose domain is already connected is told so rather than sent to add it again.",
      +  "type": "boolean"
      +}
  8. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=true and openWorldHint=true; the description goes far beyond by explaining that publishing is always live, that a first publish only shows a form and publishes nothing until the user presses Publish, and that Stripe/Shippo gaps cause a refusal with nothing published plus a recovery path. It also discloses the side effect that mobile test builds are started elsewhere on floot.com.

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 critical constraint (publishes live, never ask test or live) is front-loaded and the refusal/recovery path is clearly sequenced. It is dense with long compound sentences and repeats the live-publishing idea, but nearly every clause carries operational information the agent needs.

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?

For a destructive, externally visible mutation with six parameters and no output schema, the description covers prerequisites, per-scenario argument behavior, failure modes and the exact follow-up action after a refusal. Nothing an agent needs to call it safely and correctly appears to be missing.

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 high (83%), so the schema already carries most parameter meaning and a 3 is the baseline. The description still adds cross-parameter context the schema states only per-field: that a live app needs nothing passed, and that a first publish without a domain routes the user to the publish form.

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?

The first clause names a specific verb and resource ('Publish the app to production') and immediately enumerates the three distinct scenarios it covers: first publish, a new publish of live changes, and custom domain setup. An agent can distinguish this from unpublish_app or get_publish_status without opening any schema.

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?

It gives an explicit prerequisite ('Read get_guides('publishing') before your first call'), states which cases require no arguments ('A live app publishes at once, nothing to pass or confirm'), and directs the agent to get_publish_status for the mobile allowance. The mobile branch even tells the agent what not to ask the user ('never ask the user test or live').

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