Skip to main content
Glama

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

Update page

update_page
DestructiveIdempotent

Update a page: name (changes the slug), SEO, home/404/hidden flags, per-page headCode/bodyClass, hideHeader/hideFooter/hideChrome, pathPattern (dynamic detail-page URL). A page without seo.title / seo.description falls back to the site title (update_site), not its name. headCode holds third-party code, not page content. Guide: get_style_reference({ topic: "pages" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSite id.
seoNoPer-page SEO fields to set.
nameNoNew name; changes the slug.
pageIdYesPage id from list_pages.
headCodeNoRaw HTML for this page's <head>, server-rendered. Empty string clears. Site-wide: ROOT.props.inject.head.
isHiddenNoHidden pages aren't reachable by URL.
bodyClassNoClasses on <body> for this page. Empty string clears.
is404PageNoMake it the 404 page.
hideChromeNoHide ALL ROOT-level chrome (header, footer, sticky bars, drawers) — for ad landing pages.
hideFooterNoHide the global footer on this page.
hideHeaderNoHide the global header on this page.
isHomePageNoMake it home (unsets the current one).
pathPatternNoURL 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Site id. Pass it on every call."New value: +"Site id."
  2. Changed1 schema field changed
    • 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"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already flag destructive=true, idempotent=true, openWorld=false, so the safety profile is covered. The description adds genuine behavioral detail beyond them: renaming changes the slug, empty strings clear headCode/bodyClass, isHomePage unsets the current home page, isHidden pages aren't URL-reachable, and hideChrome targets ad landing pages. It stops short of warning that a slug change breaks existing links.

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-loads the list of updatable areas, then adds non-obvious caveats (fallback behavior, clearing semantics) and a guide pointer. Some of the field enumeration restates the schema, but the sentences carrying unique constraints justify their length.

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 13-parameter mutation tool with a nested seo object, the description covers side effects (slug change, home reassignment), clearing semantics, and fallback rules, while annotations carry the safety profile and no output schema exists. An agent has enough to call it correctly.

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 100%, so the baseline is 3, but the description adds semantics not present in the schema: the seo.title/seo.description fallback to the site title rather than the page name, and that headCode is for third-party code rather than page content. Most other field notes (slug change, pathPattern format) duplicate the 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?

Opens with a specific verb+resource ('Update a page') and enumerates the exact field groups it touches (name/slug, SEO, home/404/hidden flags, headCode/bodyClass, chrome hiding, pathPattern). This clearly separates it from siblings like add_page, delete_page, and update_site.

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?

Usage is implied rather than stated: it notes that site-level fallback behavior belongs to update_site and points to get_style_reference({ topic: "pages" }) for guidance, which is useful routing. But it never says explicitly when to choose this over add_page/delete_page or that it is the tool for modifying an existing page found via list_pages, leaving the agent to infer.

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

All PageHub toolsInspect
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