PageHub

Update page

update_page

DestructiveIdempotent

Update a page record: name (changes the slug), SEO, home/404/hidden flags, pathPattern, and policy: a password, who may open it (access conditions and what a denied visitor gets), a body class, per-page CSS variable overrides. Head code and hiding the header/footer are edits to the page file. list_pages({ pageId }) shows a page's current policy. Takes effect for visitors on publish. Guide: get_style_reference({ topic: "pages" }).

Input Schema

Name	Required	Description
`id`	No	Site id.
`seo`	No	Per-page SEO fields to set.
`name`	No	New name; changes the slug.
`pageId`	Yes	Page id from list_pages.
`policy`	No	Page policy; each key merges, and "" or [] clears it. password: text (stored hashed, never shown back). access: condition groups, OR'd, [{ logic: "all"\|"any", conditions: [{ type: "auth", key: "status", operator: "equals", value: "logged-in" }] }]. failAction + redirectUrl \| fallbackPath: what a denied visitor gets. bodyClass: classes for <body>. themeOverrides: [{ varName: "primary", value: "oklch(...)" }] CSS variables for this page.
`isHidden`	No	Hidden pages aren't reachable by URL.
`is404Page`	No	Make it the 404 page.
`isHomePage`	No	Make it home (unsets the current one).
`pathPattern`	No	URL tail AFTER the page's own slug, for detail pages. Segments: literal or `:param`, no leading slash: `:slug` on page "Car" serves /car/<slug>. Read captures as `request.params.<name>`. Empty string clears.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026
- addedInput schema / properties / seo / properties / ogVideo
```
Added value: +{
+  "maxLength": 2048,
+  "type": "string"
+}
```

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / policy

Added value: +{
+  "description": "Page policy; each key merges, and \"\" or [] clears it. password: text (stored hashed, never shown back). access: condition groups, OR'd, [{ logic: \"all\"|\"any\", conditions: [{ type: \"auth\", key: \"status\", operator: \"equals\", value: \"logged-in\" }] }]. failAction + redirectUrl | fallbackPath: what a denied visitor gets. bodyClass: classes for <body>. themeOverrides: [{ varName: \"primary\", value: \"oklch(...)\" }] CSS variables for this page.",
+  "properties": {
+    "access": {
+      "description": "Condition groups; [] removes the gate.",
+      "items": {
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "bodyClass": {
+      "description": "Extra classes on <body> for this page.",
+      "maxLength": 1024,
+      "type": "string"
+    },
+    "failAction": {
+      "description": "What a denied visitor gets.",
+      "enum": [
+        "redirect",
+        "show-page",
+        ""
+      ],
+      "maxLength": 16,
+      "type": "string"
+    },
+    "fallbackPath": {
+      "description": "Path of the page to show instead (failAction show-page), e.g. /login.",
+      "maxLength": 512,
+      "type": "string"
+    },
+    "password": {
+      "description": "Page password; \"\" removes it.",
+      "maxLength": 200,
+      "type": "string"
+    },
+    "redirectUrl": {
+      "description": "Where to send a denied visitor (failAction redirect).",
+      "maxLength": 2048,
+      "type": "string"
+    },
+    "themeOverrides": {
+      "description": "Per-page CSS variables.",
+      "items": {
+        "properties": {
+          "value": {
+            "description": "CSS value.",
+            "maxLength": 256,
+            "type": "string"
+          },
+          "varName": {
+            "description": "Variable name, with or without --.",
+            "maxLength": 64,
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed7 schema fields changedOct 25, 2026

removedInput schema / properties / bodyClass

Removed value: -{
-  "description": "Classes on <body> for this page. \"\" clears.",
-  "maxLength": 4096,
-  "type": "string"
-}

removedInput schema / properties / footerCode

Removed value: -{
-  "description": "Raw HTML at the end of this page's <body>, after its content. \"\" clears. Site-wide: ROOT.props.inject.footer.",
-  "maxLength": 65536,
-  "type": "string"
-}

removedInput schema / properties / headCode

Removed value: -{
-  "description": "Raw HTML in this page's <head>. \"\" clears. Site-wide: ROOT.props.inject.head.",
-  "maxLength": 65536,
-  "type": "string"
-}

removedInput schema / properties / hideChrome

Removed value: -{
-  "description": "Hide all ROOT-level chrome (header, footer, sticky bars, drawers).",
-  "type": "boolean"
-}

removedInput schema / properties / hideFooter

Removed value: -{
-  "description": "Hide the site footer here.",
-  "type": "boolean"
-}

removedInput schema / properties / hideHeader

Removed value: -{
-  "description": "Hide the site header here.",
-  "type": "boolean"
-}

changedInput schema / properties / pathPattern / description

Previous value: -"URL tail AFTER the page's own slug, for detail pages. Segments: literal or `:param`, no leading slash: `:slug` on page \"Car\" serves /car/<slug>. Read captures in a Data node's dataSource as `{{params.<name>}}`. Empty string clears."New value: +"URL tail AFTER the page's own slug, for detail pages. Segments: literal or `:param`, no leading slash: `:slug` on page \"Car\" serves /car/<slug>. Read captures as `request.params.<name>`. Empty string clears."

Changed7 schema fields changedOct 19, 2026

changedInput schema / properties / bodyClass / description

Previous value: -"Classes on <body> for this page. Empty string clears."New value: +"Classes on <body> for this page. \"\" clears."

addedInput schema / properties / footerCode

Added value: +{
+  "description": "Raw HTML at the end of this page's <body>, after its content. \"\" clears. Site-wide: ROOT.props.inject.footer.",
+  "maxLength": 65536,
+  "type": "string"
+}

changedInput schema / properties / headCode / description

Previous value: -"Raw HTML for this page's <head>, server-rendered. Empty string clears. Site-wide: ROOT.props.inject.head."New value: +"Raw HTML in this page's <head>. \"\" clears. Site-wide: ROOT.props.inject.head."

changedInput schema / properties / hideChrome / description

Previous value: -"Hide ALL ROOT-level chrome (header, footer, sticky bars, drawers) — for ad landing pages."New value: +"Hide all ROOT-level chrome (header, footer, sticky bars, drawers)."

changedInput schema / properties / hideFooter / description

Previous value: -"Hide the global footer on this page."New value: +"Hide the site footer here."

changedInput schema / properties / hideHeader / description

Previous value: -"Hide the global header on this page."New value: +"Hide the site header here."

changedInput schema / properties / pathPattern / description

Previous value: -"URL tail AFTER the page's own slug, for detail pages. Segments are literal or `:param`, no leading slash, no spaces: `:slug` on page \"Car\" serves /car/<slug>; `products/:handle` on \"Shop\" serves /shop/products/<handle>. Read captures in a Data node's dataSource as `{{params.<name>}}` (e.g. filter { slug: \"{{params.slug}}\" }). Empty string clears."New value: +"URL tail AFTER the page's own slug, for detail pages. Segments: literal or `:param`, no leading slash: `:slug` on page \"Car\" serves /car/<slug>. Read captures in a Data node's dataSource as `{{params.<name>}}`. Empty string clears."

Changed1 schema field changedOct 10, 2026
- changedInput schema / properties / id / description
```
Previous value: -"Site id. Pass it on every call."New value: +"Site id."
```

Changed1 schema field changedOct 4, 2026

addedInput schema / properties / pathPattern

Added value: +{
+  "description": "URL tail AFTER the page's own slug, for detail pages. Segments are literal or `:param`, no leading slash, no spaces: `:slug` on page \"Car\" serves /car/<slug>; `products/:handle` on \"Shop\" serves /shop/products/<handle>. Read captures in a Data node's dataSource as `{{params.<name>}}` (e.g. filter { slug: \"{{params.slug}}\" }). Empty string clears.",
+  "maxLength": 512,
+  "type": "string"
+}

First observedSep 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds a genuinely important trait not in the annotations: changes take effect for visitors only on publish, so a destructive edit is staged rather than immediately live. Also notes password is stored hashed and never shown back and that policy keys merge with ""/[] clearing, complementing the destructiveHint/idempotentHint annotations without contradicting them.

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?

Front-loaded with the editable field list, then supporting pointers (list_pages, publish semantics, style guide). Telegraphic and dense, but nearly every clause carries information; a slightly more explicit sentence on the page-file exclusion would help readability.

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

Completeness4/5

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

For a 9-parameter nested mutation tool with destructive semantics, the description covers scope, staging-on-publish behavior, inspection path, and where adjacent edits belong. Safety profile is already carried by annotations and field detail by the schema, so remaining gaps are minor.

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 every parameter and nested field thoroughly; the description largely restates the same fields at a summary level. Its grouping of policy sub-keys is convenient for scanning but adds little new meaning beyond what the schema provides.

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 (update) and resource (page record) and enumerates the exact editable surfaces: name/slug, SEO, home/404/hidden flags, pathPattern, and policy. An agent can distinguish it immediately from add_page, delete_page, and outline_page.

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?

Names list_pages({ pageId }) as the way to inspect current policy before changing it, and routes to get_style_reference({ topic: "pages" }) for guidance. It also implicitly excludes head code and header/footer hiding by saying those are page-file edits, though it does not name edit_site_file explicitly.

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

All PageHub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?