Skip to main content
Glama

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.
filesYesThe 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.
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.
manifestNoHow 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
validateNoCheck 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.
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. Dates show when Glama detected each change.

  1. 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."
  2. 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"
      +]
  3. 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."
  4. 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."
  5. 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"
      +}
  6. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=false, so the description carries the behavioral burden. It discloses that base version conflicts are refused, default replace deletes omitted files (destructive), merge builds on prior merges including staged versions, env is readable by anyone, secrets must already exist, and validate writes nothing. It also surfaces that a manifest replaces the whole manifest, requiring all needed fields to be resent.

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 dense but every sentence earns its place, covering the base version requirement, default behavior, merge semantics, staging, validation, and manifest replacement. It front-loads the most critical operational constraint (read first, pass base_version_id). The schema's parameter descriptions are verbose but they are structured content, not description bloat.

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 9-parameter mutation with nested objects, no output schema, and no behavioral annotations, the description manages to cover the critical workflow, destructive edge cases, merge semantics, the manifest replacement rule, secrets and env constraints, and the validate/staging paths. The only remote reference is a link to the full SKILL.md, which is acceptable because the description already summarizes 'the data plane in full, with its limits' and the link is supplementary.

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 100%, so the schema already documents every parameter, and the description doesn't repeat field-by-field details. However, the description adds cross-parameter semantics: base_version_id must come from read_app, remove only works with merge, an empty files array is valid for removals, and mode replace vs merge changes the meaning of files. That is valuable, but the schema already carries most parameter meaning, so a 3 is the right baseline.

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 specific verb and resource — 'Publish a new version of an existing app' — and immediately distinguishes it from create_app by saying it's for an existing app. The description also names publish_app_version as the sibling that makes a staged version live, so an agent can tell this tool apart from related ones.

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 and how-to-use guidance: read the app first and pass the base_version_id read_app returns, use merge only for changed files, use validate true to check without publishing, and use publish false to stage for later with publish_app_version. It also explains when not to use replace (whole file set, anything left out is gone) and flags review-before-publish behavior.

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.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target clearly distinct actions and resources, such as app CRUD, versioning, sharing, secrets, and folder operations. A few adjacent tools like read_app, read_app_file, and read_app_version, or update_app and publish_app_version, require careful reading, but their descriptions are explicit enough to prevent serious confusion.

Naming Consistency3/5

The set mostly uses a verb_noun pattern, with names like create_app, list_secrets, set_app_access, and trash_app. However, Unix-style commands like ls, mkdir, mv, tree, and whoami, plus mixed verbs such as get, read, list, remove, and revoke, break any single consistent convention.

Tool Count3/5

24 tools is on the heavy end of the 16-25 range, and while the platform covers apps, versions, folders, sharing, secrets, logs, and databases, the count feels somewhat large. Each tool has a defined role, but several could potentially be consolidated without losing clarity.

Completeness4/5

The surface covers the main lifecycle well: creating, reading, updating, versioning, sharing, securing, and organizing apps, plus secrets and database queries. Notable gaps are the lack of a permanent delete or restore tool for trashed apps, and the stated absence of captured function logs, but these are workable limitations rather than dead ends.