Skip to main content
Glama
Sign In
brewpage-mcp

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update page

update_html
Destructive

Updates an existing BrewPage page's HTML, Markdown, code, or JSON content using an owner token and returns the updated page metadata.

Instructions

Update an existing BrewPage HTML, Markdown, code or JSON page. Requires owner token. Returns the updated page metadata. Format omitted keeps the stored format, except a whole HTML document makes a Markdown page an HTML page. The link and delivery mode never change on update; an advisory deliveryModeReason and delivery notice are included when the new content uses browser features that may not work fully on a BrewPage link. Old publications (made before 5 October 2026) are read-only: 409 OLD_PUBLICATION_READ_ONLY with createUrl to publish anew. BrewPage tokens and manage links must never be in public content. 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>",
      "content": "<content>"
    },
    "name": "update_html"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPage ID
tagsNoOptional tags; replace the page's stored tags ([] clears). Omit to keep them.
stateNoPage 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).
formatNoContent 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.
contentYesNew HTML, Markdown, code or JSON content
namespaceYesPage namespace
ownerTokenNoOwner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.21.0
    • 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)."
+}
  2. Changed1 schema field changedv1.16.10
    • 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."
  3. Changed1 schema field changedv1.16.6
    • 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"
+}
  4. Changed2 schema fields changedv1.16.3
    • changedInput schema / properties / content / description
      Previous value: -"New HTML or Markdown content"New value: +"New HTML, Markdown, code or JSON content"
    • 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)."
  5. Changed2 schema fields changedv1.15.0
    • 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
  6. Changed2 schema fields changedv1.13.0
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token received when the page was created"New value: +"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."
    • changedInput schema / required
      Previous value: -[
-  "namespace",
-  "id",
-  "content",
-  "ownerToken"
-]New value: +[
+  "namespace",
+  "id",
+  "content"
+]
  7. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description goes much further by disclosing invariants (link and delivery mode never change on update), conditional advisories (deliveryModeReason and a delivery notice when new content uses browser features), a specific failure mode with error code and remediation URL, and policy constraints around tokens, manage links and badge modification. That is exactly the kind of context that annotations cannot carry, and it materially shapes correct invocation.

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?

Purpose, auth and return value are front-loaded, then the fallback and error semantics follow in a logical order with no filler sentences. It is dense but slightly sprawling, mixing operational behavior with standing policy notes (public-content tokens, badge rules) that read more like guardrails than invocation guidance.

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, the description covers the prerequisite (owner token), the return ('updated page metadata'), format fallback, immutable fields, and a named error with remediation. Nothing an agent needs in order to call this correctly appears to be missing.

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 description coverage is 100%, so the baseline is 3, and the description largely restates what the schema already says about format omission ('Format omitted keeps the stored format...'). The one incremental clarification is the HTML-document-overrides-Markdown rule, but it duplicates the format parameter's own description rather than adding new meaning.

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 scope: 'Update an existing BrewPage HTML, Markdown, code or JSON page', which cleanly separates it from the create-side siblings (publish_html, publish_json). It also states the auth prerequisite and the return shape in the same breath, so an agent knows what it is invoking without opening the schema.

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

Usage Guidelines4/5

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

It establishes the usage context (existing page, owner token required) and gives one concrete exclusion path: old publications are read-only and return 409 OLD_PUBLICATION_READ_ONLY with a createUrl to publish anew. What is missing is an explicit 'to create a new page use publish_html' routing statement, though the 'existing' qualifier plus the createUrl hint makes it inferable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools