Skip to main content
Glama

Update page or site

update_html
DestructiveIdempotent

Replace the content of an existing page (content) or every file of an existing site (files; files absent from the upload are removed). The link stays. Page code must not hide or alter the BrewPage badge; a profile can turn the badge off for a page.

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": {
      "namespace": "<namespace>",
      "id": "<id>"
    },
    "name": "update_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
tagsNoReplace the stored tags
entryNoSite entry file, default index.html
filesNoSite files; instead of `content`
stateNoNamed lists are added or updated; `null` turns Page data off
formatNoOmitted: the stored format stays
contentNo
namespaceYes
ownerTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / content / description
      Removed value: -"New HTML, Markdown, code or JSON content"
    • addedInput schema / properties / entry
      Added value: +{
      +  "description": "Site entry file, default index.html",
      +  "type": "string"
      +}
    • addedInput schema / properties / files
      Added value: +{
      +  "description": "Site files; instead of `content`",
      +  "items": {
      +    "properties": {
      +      "content": {
      +        "type": "string"
      +      },
      +      "path": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "path",
      +      "content"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / format / description
      Previous value: -"Content format. Accepts (case-insensitive on html/markdown): 'html', 'markdown'/'md', or a code language — yaml, json, xml, csv, tsv, log, toml, ini, sql, sh, bat, env, javascript, typescript, tsx, jsx, css, properties, docker, txt. Omit to preserve the stored format, except a whole HTML document makes a Markdown page an HTML page."New value: +"Omitted: the stored format stays"
    • removedInput schema / properties / id / description
      Removed value: -"Page ID"
    • removedInput schema / properties / namespace / description
      Removed value: -"Page namespace"
    • removedInput schema / properties / ownerToken / description
      Removed value: -"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
    • removedInput schema / properties / state / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": {},
      -    "propertyNames": {
      -      "type": "string"
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / state / description
      Previous value: -"Page data config, same shape as on create. Lists named here are added or updated, the others stay; a stored list keeps its `mode` and `write` when the call omits them. Omitted: the stored config stays; `null` turns page data off (saved entries are kept)."New value: +"Named lists are added or updated; `null` turns Page data off"
    • addedInput schema / properties / state / type
      Added value: +[
      +  "object",
      +  "null"
      +]
    • changedInput schema / properties / tags / description
      Previous value: -"Optional tags; replace the page's stored tags ([] clears). Omit to keep them."New value: +"Replace the stored tags"
    • changedInput schema / required
      Previous value: -[
      -  "namespace",
      -  "id",
      -  "content"
      -]New value: +[
      +  "namespace",
      +  "id"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / state
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Page data config, same shape as on create. Lists named here are added or updated, the others stay; a stored list keeps its `mode` and `write` when the call omits them. Omitted: the stored config stays; `null` turns page data off (saved entries are kept)."
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / format / description
      Previous value: -"Content format. Accepts (case-insensitive on html/markdown): 'html', 'markdown'/'md', or a code language — yaml, json, xml, csv, tsv, log, toml, ini, sql, sh, bat, env, javascript, typescript, tsx, jsx, css, properties, docker, txt. Omit to preserve the stored format."New value: +"Content format. Accepts (case-insensitive on html/markdown): 'html', 'markdown'/'md', or a code language — yaml, json, xml, csv, tsv, log, toml, ini, sql, sh, bat, env, javascript, typescript, tsx, jsx, css, properties, docker, txt. Omit to preserve the stored format, except a whole HTML document makes a Markdown page an HTML page."
  4. Changed1 schema field changed
    • addedInput schema / properties / tags
      Added value: +{
      +  "description": "Optional tags; replace the page's stored tags ([] clears). Omit to keep them.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  5. Changed1 schema field changed
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."New value: +"Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  6. Changed1 schema field changed
    • changedInput schema / properties / content / description
      Previous value: -"New HTML or Markdown content"New value: +"New HTML, Markdown, code or JSON content"
  7. 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
  8. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses important destructive behavior: files absent from the upload are removed. It also states that the link stays and explains the BrewPage badge constraint, which is useful operational context. It still does not cover auth/ownerToken requirements or side effects on tags and state.

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?

The description is front-loaded with the core replace operation and stays compact across three sentences. Each sentence contributes useful information: the page/site distinction, the file-removal behavior, the stable link, and the badge constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with nine parameters, no output schema, and only 56% schema coverage, the description covers the core behavior and key destructive nuance well. It is still incomplete regarding auth/ownerToken expectations, non-content parameter effects, and what a caller should expect on return.

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?

With 56% schema description coverage, the description meaningfully clarifies the main `content` versus `files` modes and the destructive file-removal semantics. It does not add meaning for several other parameters such as `tags`, `state`, `format`, `entry`, and `ownerToken`, so it only partially compensates for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: replace the content of an existing page (`content`) or every file of an existing site (`files`). It clearly distinguishes page mode from site mode and emphasizes that the target must already exist, though it does not explicitly name sibling alternatives such as publish_html.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives mode-selection guidance by explaining that `content` updates a page while `files` updates a site, and it warns that files absent from the upload are removed. However, it does not explicitly say when to use this tool versus publish_html, update_json, or other siblings, nor does it state prerequisites for either mode.

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.