Skip to main content
Glama

Replace a page's content

update_page
DestructiveIdempotent

Replace the content of an existing page in place: the same URL serves the new content immediately, so links the human already shared keep working. Use this instead of publish_page whenever the page already exists. The previous version stays restorable from the dashboard for 7 days (Pro keeps full version history). Pass draft: true to stage the update instead: nothing changes for viewers until the maker reviews the previewUrl and presses "Sync to live"; use it when the human asked to see changes before they go out. Fails with page_not_found if the id is not a live or offline page in this space, and with secrets_detected (nothing changes) if the new content looks like it holds live credentials. A page that works as a sign-in or payment form sending what people type to another site can be refused with unsafe_page_detected (no override): make such forms non-functional demos. Connected without an API key, it updates a preview instead: pass the claim_token that publish_page returned (or omit it in the same session that published the page). The URL stays the same and the 7-day expiry does not move; previews have no drafts or version history. After the human claims the preview (claim_page), a page that moved into their account answers preview_already_claimed: reconnect with their API key to keep updating it. Pages that did not fit their plan stay previews and the claim token still updates them.

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_id": "<page_id>",
      "html": "<html>"
    },
    "name": "update_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
htmlYesThe complete new document (not a diff). HTML, or Markdown when source_type is "markdown".
draftNoDefault false (publishes live instantly). true = stage the update; relay the returned previewUrl so the human can review and press Sync. A new draft replaces any pending one.
titleNoOptional; omit to keep the existing title.
page_idYesThe page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible.
projectNoOptional; omit to keep the existing project.
claim_tokenNoKeyless previews only: the claimToken publish_page returned for this page. Ignored when connected with an API key.
source_typeNoDefault "html".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / claim_token
      Added value: +{
      +  "description": "Keyless previews only: the claimToken publish_page returned for this page. Ignored when connected with an API key.",
      +  "type": "string"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / html / description
      Added value: +"The complete new document (not a diff). HTML, or Markdown when source_type is \"markdown\"."
    • changedInput schema / properties / page_id / description
      Previous value: -"The id returned by publish_page / list_pages."New value: +"The page id: the `id` field from publish_page or list_pages (also the last path segment of the page URL, …/docs/<page_id>). Only pages in the connected maker's space are visible."
    • addedInput schema / properties / source_type / description
      Added value: +"Default \"html\"."
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations only declare destructive/idempotent/openWorld, whereas the description discloses the recoverability window (7 days, Pro full history), that drafts gate visibility until the maker presses Sync, that previews have no drafts or version history, and the exact failure modes (page_not_found, secrets_detected with 'nothing changes', unsafe_page_detected with no override, preview_already_claimed). The one gap is that it never says what the success response contains beyond mentioning a previewUrl in passing, so the agent must infer the return shape.

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

Conciseness3/5

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

The purpose and the publish_page alternative are correctly front-loaded, and almost every sentence carries decision-relevant information. However, roughly a dozen distinct topics — versioning, drafts, four error codes, keyless previews, claim flow, plan limits — are crammed into a single undifferentiated paragraph, making it easy for an agent to lose the thread before reaching the preview_already_claimed case.

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 7-parameter destructive mutation with no output schema and two distinct auth modes, the description covers identity of the page, in-place URL preservation, staging, recoverability, and the full set of error branches an agent must handle. Little that matters for a correct call is left out.

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 already 100%, so 3 is the baseline, but the description adds real meaning: it explains the consequence of draft:true (viewers see nothing until Sync) and the claim_token requirement for keyless previews (pass the token publish_page returned, or omit in the same session). These are behavioral semantics the schema's short field notes do not convey.

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 opening sentence states a specific verb and resource — 'Replace the content of an existing page in place' — and immediately names the sibling it is not: 'Use this instead of publish_page whenever the page already exists.' An agent can distinguish it from publish_page without opening either 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 explicit routing rules (use this rather than publish_page when the page exists), a conditional mode ('Pass draft: true ... use it when the human asked to see changes before they go out'), and keyless-preview handling with claim_token. It also says when an operation will be refused, which is guidance no sibling list could convey.

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