Skip to main content
Glama

Update a published page in place

update_page

Change a page you already published, keeping the SAME private link. Use this whenever the user wants to update, edit, revise, fix, re-publish, rename, re-file, password-protect, or change the expiry of a page you previously created — do NOT call create_page for any of that, which would mint a new throwaway link. Identify the page with page (its viewer URL or slug, e.g. from create_page or list_pages). Every change field is optional and independent: pass only what you want to change, and anything you omit is left exactly as-is. You must pass at least one of html, title, password, expiry, or project. html swaps the content as a new version (the previous version stays in the 30-day history). password sets a viewer password, or pass an empty string "" to REMOVE the password — note a searchable page can't take a password. expiry is one of '1d' | '7d' | '30d' | 'never' ('never' pins the page always-on; the Free tier is limited to '7d' or 'never', and on Free '7d' only takes a page off always-on, where it resumes the countdown it had when it was pinned — it never extends a page that is already counting down or revives an expired one). title renames it; project re-files it under a project by name (created if it doesn't exist). If the page was SHARED with you (you're a collaborator, see list_pages), you may only pass html — title, password, expiry and project stay the owner's; the owner is emailed when you push. SIZE LIMIT: the html argument travels as text (roughly under ~100 KB). For a larger content swap, don't use this tool: if you can run shell commands, call prepare_upload with page set to this page, curl the file, then finish_upload — that replaces the content and keeps the SAME link; otherwise tell the user to re-upload with the miinideck CLI or the web uploader.

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": {
      "page": "<page>"
    },
    "name": "update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlNoOptional. The complete, self-contained HTML document (including <!doctype html>) to publish as the new version. Omit to leave the content unchanged.
pageYesThe page's viewer URL or its slug (the part after the last '/').
titleNoOptional new title shown in the owner's dashboard. Pass an empty string to clear it. Omit to leave unchanged.
expiryNoOptional new expiry. 'never' pins the page always-on. Free tier may only pick '7d' or 'never'; on Free, '7d' can't extend a page that is already counting down. Omit to leave unchanged.
projectNoOptional project (folder) to move this page under, BY NAME. Matches an existing project case-insensitively, or creates a new one. Omit to leave unchanged.
passwordNoOptional. Set a viewer password, or pass an empty string "" to remove an existing one. Rejected if the page is searchable. Omit to leave unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does substantial work: html swaps content as a new version with the prior version kept in a 30-day history, password "" removes protection, a searchable page cannot take a password, Free-tier expiry '7d' only unpins rather than extends, and a collaborator's push emails the owner. It still omits response shape and whether a no-op/unchanged call is idempotent, and the ~100 KB limit is hedged ('roughly under ~100 KB') rather than stated as a hard rule.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Long, but front-loaded with the core action and the create_page exclusion before diving into per-field details, and nearly every sentence carries a distinct operational fact (versioning, password removal, tier math, size limit, fallback path). A minor amount is duplicated from the schema, but the density justifies the length.

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 six-parameter mutation tool with no annotations and no output schema, the description covers the destructive/versioning implications, permission differences for collaborators, tier-specific expiry behavior, and the escape hatch for oversize payloads. Nothing an agent needs in order to call this correctly or to avoid the wrong sibling 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 100%, so the baseline is 3, but the description adds a constraint the schema does not encode: at least one of `html`, `title`, `password`, `expiry`, or `project` must be passed, and omitted fields are left exactly as-is. It also repeats the schema's enum/tier and empty-string-removal semantics, which is redundant but reinforces the key edge cases, and adds the collaborator field restriction that the schema does not express.

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 verb and resource ('Change a page you already published') plus the distinguishing invariant ('keeping the SAME private link'), and explicitly contrasts with create_page, which would 'mint a new throwaway link'. An agent can separate this from create_page and from the upload siblings without opening a 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?

Gives an explicit trigger list (update, edit, revise, fix, re-publish, rename, re-file, password-protect, change expiry) and an explicit exclusion ('do NOT call create_page for any of that'). It also routes the oversize case to prepare_upload + curl + finish_upload, or to the CLI/web uploader when shell access is unavailable, and carves out the collaborator case where only `html` is permitted.

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