Skip to main content
Glama

Publish a new version

update_app

Publish a new version of an existing app. Read the app first and pass the base_version_id read_app returns: it names the version this edit builds on, and a base that has moved is refused rather than overwritten. By default the new version replaces the whole file set and goes live immediately unless the app is set to review before publishing. Send mode merge to publish only the files that changed and keep the rest of that version's files, with remove for paths to drop. Two merges in a row build on each other, staged versions included. Send validate true to check the call without publishing, or publish false to stage the version and make it live later with publish_app_version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoreplace, the default, publishes files as the whole file set: anything left out is gone. merge sends only the files that changed and carries every other file of the base version into the new version.
filesYesFiles to publish as plain text, not base64: HTML, Markdown or JavaScript exporting default { fetch }. A page serves index.html at its URL. Functions declaring db include schema changes as migrations/NNNN_name.sql, run in order when the version goes live.
app_idYesThe app id, as returned by search_apps or create_app. Starts with app_.
removeNoPaths from the base version to leave out of the new one. Merge only, and a path that is not in the base version is refused rather than ignored. A call that only removes files sends an empty files array.
messageNoWhat changed in this version.
publishNofalse stages the version instead of putting it on the link. It is built and readable at its own version URL, and publish_app_version makes it live. Defaults to true.
manifestNoOmit on create_app for a static page; omit on update_app to keep the previous version's manifest. If supplied, replaces the entire manifest: include every field still needed. services, secrets and env apply only to functions. Runtime details and limits: https://reachpad.dev/SKILL.md
validateNoCheck without writing. Validates and returns the resulting file set, total bytes, entry and kind. create_app also validates the slug and returns it with the URL; <tag> stands for five random characters assigned on publish. Does not check the org app limit; publishing can still fail for that.
base_version_idYesThe base_version_id read_app returned, which is the version this edit was made against. Starts with ver_.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"The files to publish. Content is plain text written here in the chat, not base64: an HTML page, a Markdown document, or a JavaScript module that exports default { fetch }. A page app serves index.html at the app URL. A function that declares the db service carries its schema changes here too, as migrations/NNNN_name.sql, which run in order when the version goes live."New value: +"Files to publish as plain text, not base64: HTML, Markdown or JavaScript exporting default { fetch }. A page serves index.html at its URL. Functions declaring db include schema changes as migrations/NNNN_name.sql, run in order when the version goes live."
    • changedInput schema / properties / manifest / description
      Previous value: -"How the version runs. Omit it on create_app for a static page, and omit it on update_app to keep the previous version's manifest. A manifest that is sent replaces the whole of it, so send every field the app still needs. services, secrets and env are read by a function only. The data plane in full, with its limits: https://reachpad.dev/SKILL.md"New value: +"Omit on create_app for a static page; omit on update_app to keep the previous version's manifest. If supplied, replaces the entire manifest: include every field still needed. services, secrets and env apply only to functions. Runtime details and limits: https://reachpad.dev/SKILL.md"
    • changedInput schema / properties / manifest / properties / entry / description
      Previous value: -"For a page, the file served at the root of the link, usually index.html. For a function, the module that exports default { fetch }. It has to be one of the files the version ends up with, which on a merge includes the ones carried over from the base."New value: +"Root file for a page, usually index.html; module exporting default { fetch } for a function. Must exist in the resulting files, including files retained by merge."
    • changedInput schema / properties / manifest / properties / env / description
      Previous value: -"Plain string values a function reads as env.NAME. Stored as written and readable by anyone who can read the version, so put a key in secrets instead. A name that is also in secrets fails the publish."New value: +"Plain strings bound as env.NAME, visible to anyone who can read the version. Put keys in secrets instead. Names shared with secrets fail publication."
    • changedInput schema / properties / manifest / properties / kind / description
      Previous value: -"page serves the files as they are. function runs one JavaScript module for every request to the link."New value: +"page serves files unchanged; function runs a JavaScript module for every request."
    • changedInput schema / properties / manifest / properties / secrets / description
      Previous value: -"Names of secrets the organization has already set, each bound as env.NAME. A function only. Set the value first, in Settings at reachpad.dev/apps/settings/secrets or with reachpad secrets set NAME: a name the organization has not set fails the publish with NAME is not set."New value: +"Organization secret names bound as env.NAME for functions. Set values first at reachpad.dev/apps/settings/secrets or with reachpad secrets set NAME. An unset name fails publication with NAME is not set."
    • changedInput schema / properties / manifest / properties / services / description
      Previous value: -"What the function may use, on env.reachpad: db is the app's own SQLite database, through env.reachpad.db.query(sql, params) and env.reachpad.db.batch(statements); files is its file store, through env.reachpad.files.put/get/head/delete. A function only, and any other name is refused when you publish. Declaring db also lets the version carry migrations/NNNN_name.sql, which run when it goes live."New value: +"Function services: db binds the app's SQLite database at env.reachpad.db.query(sql, params) and env.reachpad.db.batch(statements); files binds its file store at env.reachpad.files.put/get/head/delete. Other names are refused. db permits migrations/NNNN_name.sql, run when the version goes live."
    • changedInput schema / properties / validate / description
      Previous value: -"Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind, and on create_app the slug and the URL the app would take, where <tag> stands for the five random characters drawn when it is published. It checks the file set, its total size, that the entry file is one of the files, and on create_app that the slug is a usable link name. It does not check the org's app limit, so a create that would be refused for that is still refused when it is published."New value: +"Check without writing. Validates and returns the resulting file set, total bytes, entry and kind. create_app also validates the slug and returns it with the URL; <tag> stands for five random characters assigned on publish. Does not check the org app limit; publishing can still fail for that."
  2. Changed1 schema field changed
    • changedInput schema / properties / manifest / properties / secrets / description
      Previous value: -"Names of secrets the organization has already set, each bound as env.NAME. A function only. Set the value first, in Settings at reachpad.dev/apps/settings or with reachpad secrets set NAME: a name the organization has not set fails the publish with NAME is not set."New value: +"Names of secrets the organization has already set, each bound as env.NAME. A function only. Set the value first, in Settings at reachpad.dev/apps/settings/secrets or with reachpad secrets set NAME: a name the organization has not set fails the publish with NAME is not set."
  3. Changed1 schema field changed
    • changedInput schema / properties / validate / description
      Previous value: -"Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind. It checks the file set, its total size, and that the entry file is one of the files. It does not check the org's app limit or whether the slug is free, so a create that would be refused for one of those is still refused when it is published."New value: +"Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind, and on create_app the slug and the URL the app would take, where <tag> stands for the five random characters drawn when it is published. It checks the file set, its total size, that the entry file is one of the files, and on create_app that the slug is a usable link name. It does not check the org's app limit, so a create that would be refused for that is still refused when it is published."
  4. Changed8 schema fields changed
    • changedInput schema / properties / files / description
      Previous value: -"The files to publish. Content is plain text written here in the chat, not base64: an HTML page, a Markdown document, or a JavaScript module that exports default { fetch }. A page app serves index.html at the app URL."New value: +"The files to publish. Content is plain text written here in the chat, not base64: an HTML page, a Markdown document, or a JavaScript module that exports default { fetch }. A page app serves index.html at the app URL. A function that declares the db service carries its schema changes here too, as migrations/NNNN_name.sql, which run in order when the version goes live."
    • changedInput schema / properties / manifest / description
      Previous value: -"How the version runs. Omit it for a static page. kind is page or function, entry is the file served at / for a page or the module for a function."New value: +"How the version runs. Omit it on create_app for a static page, and omit it on update_app to keep the previous version's manifest. A manifest that is sent replaces the whole of it, so send every field the app still needs. services, secrets and env are read by a function only. The data plane in full, with its limits: https://reachpad.dev/SKILL.md"
    • addedInput schema / properties / manifest / properties / entry / description
      Added value: +"For a page, the file served at the root of the link, usually index.html. For a function, the module that exports default { fetch }. It has to be one of the files the version ends up with, which on a merge includes the ones carried over from the base."
    • changedInput schema / properties / manifest / properties / env / description
      Previous value: -"Plain string values readable by a function."New value: +"Plain string values a function reads as env.NAME. Stored as written and readable by anyone who can read the version, so put a key in secrets instead. A name that is also in secrets fails the publish."
    • addedInput schema / properties / manifest / properties / kind / description
      Added value: +"page serves the files as they are. function runs one JavaScript module for every request to the link."
    • addedInput schema / properties / manifest / properties / secrets / description
      Added value: +"Names of secrets the organization has already set, each bound as env.NAME. A function only. Set the value first, in Settings at reachpad.dev/apps/settings or with reachpad secrets set NAME: a name the organization has not set fails the publish with NAME is not set."
    • addedInput schema / properties / manifest / properties / services / description
      Added value: +"What the function may use, on env.reachpad: db is the app's own SQLite database, through env.reachpad.db.query(sql, params) and env.reachpad.db.batch(statements); files is its file store, through env.reachpad.files.put/get/head/delete. A function only, and any other name is refused when you publish. Declaring db also lets the version carry migrations/NNNN_name.sql, which run when it goes live."
    • addedInput schema / properties / manifest / properties / services / items / enum
      Added value: +[
      +  "db",
      +  "files"
      +]
  5. Changed3 schema fields changed
    • changedInput schema / properties / base_version_id / description
      Previous value: -"The id of the version this edit was made against, from read_app. Starts with ver_."New value: +"The base_version_id read_app returned, which is the version this edit was made against. Starts with ver_."
    • changedInput schema / properties / mode / description
      Previous value: -"replace, the default, publishes files as the whole file set: anything left out is gone. merge sends only the files that changed and carries every other file of the live version into the new version."New value: +"replace, the default, publishes files as the whole file set: anything left out is gone. merge sends only the files that changed and carries every other file of the base version into the new version."
    • changedInput schema / properties / remove / description
      Previous value: -"Paths from the live version to leave out of the new one. Merge only, and a path that is not in the live version is refused rather than ignored. A call that only removes files sends an empty files array."New value: +"Paths from the base version to leave out of the new one. Merge only, and a path that is not in the base version is refused rather than ignored. A call that only removes files sends an empty files array."
  6. Changed1 schema field changed
    • changedInput schema / properties / validate / description
      Previous value: -"Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind. Nothing is published, so a version that would be refused is refused before it reaches the link."New value: +"Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind. It checks the file set, its total size, and that the entry file is one of the files. It does not check the org's app limit or whether the slug is free, so a create that would be refused for one of those is still refused when it is published."
  7. Changed4 schema fields changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "replace, the default, publishes files as the whole file set: anything left out is gone. merge sends only the files that changed and carries every other file of the live version into the new version.",
      +  "enum": [
      +    "replace",
      +    "merge"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / publish
      Added value: +{
      +  "description": "false stages the version instead of putting it on the link. It is built and readable at its own version URL, and publish_app_version makes it live. Defaults to true.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / remove
      Added value: +{
      +  "description": "Paths from the live version to leave out of the new one. Merge only, and a path that is not in the live version is refused rather than ignored. A call that only removes files sends an empty files array.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / validate
      Added value: +{
      +  "description": "Check the call and write nothing. Answers with the file set the publish would contain, its total bytes, the entry and the kind. Nothing is published, so a version that would be refused is refused before it reaches the link.",
      +  "type": "boolean"
      +}
  8. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only provide readOnlyHint=false, idempotentHint=false, destructiveHint=false, leaving behavioral burden to the description. The description thoroughly discloses side effects: 'replace publishes files as the whole file set: anything left out is gone,' merge semantics, that base-a-move is refused rather than overwritten, that it goes live immediately unless review/publish=false, and that two merges build on each other. It also notes validation side-effects (returns file set, bytes, entry, kind) and the org limit failure case. No annotation contradiction.

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 description is long but dense, covering many behaviors without fluff. It is front-loaded with the core action and prerequisite, then explains modes, validation, and staging. Despite being a single paragraph, each sentence earns its place. Minor improvement could be bullet points, but the structure is logical and readable.

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?

The tool is complex (9 params, nested objects, no output schema), and the description covers almost everything an agent needs: prerequisites, mode semantics, validation return info, staging, merge accumulation, manifest replacement rules, and failure modes. It omits a general description of the return value for the normal publish call (unlike the validate case), but references SKILL.md for runtime details. This is near-complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds substantial meaning beyond the schema. For example, it explains merge mode in the narrative, clarifies that files are plain text not base64, describes how functions with db include migrations, and links to SKILL.md for runtime details. It also clarifies base_version_id semantics ('the version this edit builds on') and the behavior of validate and publish flags. This goes well beyond the schema.

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 description states a clear specific verb and resource: 'Publish a new version of an existing app.' It distinguishes itself from create_app (new app) and publish_app_version (making a staged version live) by explicitly naming the latter and explaining the staging flow. The purpose is unambiguous.

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?

The description gives explicit workflow guidance: read the app first, pass base_version_id, and mentions alternatives like publish_app_version for later publication. It explains when to use merge vs replace, when to use validate=true, and when to use publish=false for staging. It also warns about refusal conditions (base moved, path not in base). This is comprehensive usage direction.

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.