brewpage-mcp

Change delivery mode

update_hosting

Changes the delivery mode (path or dedicated subdomain) for a new publication using an owner token; optionally checks hostingVersion and reports mismatches without rejecting stale values.

Instructions

Change delivery mode for a NEW publication (not a site, not a non-public HTML-format page). Requires owner token; optional expectedVersion = current hostingVersion. Mismatches are reported, not rejected: a stale version still applies, and OLD links or forced subdomain modes stay unchanged; the result then carries a delivery notice. Content updates never change hosting.

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

Input Schema

Name	Required	Description
`id`	Yes	Resource ID
`type`	Yes	Resource type; sites always stay on their own subdomain
`namespace`	Yes	Resource namespace; non-public HTML-format pages stay on subdomain
`ownerToken`	No	Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).
`deliveryMode`	Yes	path = Promotion; subdomain = Dedicated subdomain
`expectedVersion`	No	Optional current hostingVersion from the server; a stale value still applies and the result says so

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.16.3Oct 30, 2026

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)."

Changed2 schema fields changedv1.15.0Oct 27, 2026

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
```

Changed2 schema fields changedv1.13.0Oct 25, 2026

changedInput schema / properties / ownerToken / description

Previous value: -"Original resource owner token"New value: +"Owner token from create. Default: BREWPAGE_OWNER_TOKEN."

changedInput schema / required

Previous value: -[
-  "type",
-  "namespace",
-  "id",
-  "ownerToken",
-  "deliveryMode"
-]New value: +[
+  "type",
+  "namespace",
+  "id",
+  "deliveryMode"
+]

First observedv0.1.0Oct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses that an owner token is required, that expectedVersion mismatches are reported rather than rejected, that stale versions still apply, that old links or forced subdomain modes stay unchanged, and that the result carries a delivery notice. These are exactly the mutation semantics an agent needs before invoking the tool.

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 action and eligibility constraints, then packs auth, versioning, and non-destructive behavior into dense but useful sentences. Every sentence carries operational information with no filler.

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 output schema, the description covers eligibility, required auth, version mismatch behavior, link/subdomain preservation, and the delivery-notice outcome. It is complete enough for an agent to call the tool correctly without inferring missing behavior.

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 schema already documents all six parameters, including ownerToken defaults, deliveryMode enum meanings, and expectedVersion behavior. The description reinforces expectedVersion and owner-token requirements but adds little parameter-level meaning beyond the structured schema.

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 description states a specific verb and resource, 'Change delivery mode,' and immediately narrows scope to a NEW publication while excluding sites and non-public HTML-format pages. This lets an agent distinguish it from content-update siblings such as update_html and update_json.

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 gives clear when-to-use context through eligibility constraints ('NEW publication,' not a site, not a non-public HTML-format page) and says content updates never change hosting. It does not explicitly name alternative sibling tools, but the exclusions provide enough routing guidance.

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