PageHub

Update site

update_site

DestructiveIdempotent

Set the site's name, title, description, ogImage, ogVideo, indexing, AI crawlers, timezone, language or mount origin/key — immediate, no publish. title/description/og*: fallbacks for pages without their own seo. "" clears. Details: get_style_reference({ topic: "site" }).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "update_site"
  }
}

Input Schema

Name	Required	Description
`id`	No	Site id.
`name`	No	URL slug (subdomain): lowercase letters, digits, hyphens.
`title`	No	Fallback <title>.
`ogImage`	No	https URL, 1200×630.
`ogVideo`	No	MP4 URL.
`language`	No	<html lang> tag: "uk", "pt-BR"… "" = en.
`timezone`	No	The business's IANA zone, e.g. "America/Los_Angeles". Liquid dates (date, time_tag), {{ year }}, {{ site.timezone }} and the times in notification emails use it. "" = UTC.
`crawlMode`	No	public = indexed. noindex = viewable by link, kept out of search (a client copy not yet on its domain). private_preview = noindex + robots.txt Disallow.
`description`	No	Fallback meta description.
`mountOrigin`	No	Origin of the Next.js app serving it via @pagehub/next, e.g. "https://app.example.com".
`rotateMountKey`	No	true issues a new mount key (shown once), voiding the old one.
`blockAiCrawlers`	No	true blocks AI crawlers in robots.txt and turns off /llms.txt; search engines unaffected.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / ogVideo

Added value: +{
+  "description": "MP4 URL.",
+  "maxLength": 2048,
+  "type": "string"
+}

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / timezone / description

Previous value: -"IANA zone for notification emails, e.g. \"America/Los_Angeles\". \"\" = UTC."New value: +"The business's IANA zone, e.g. \"America/Los_Angeles\". Liquid dates (date, time_tag), {{ year }}, {{ site.timezone }} and the times in notification emails use it. \"\" = UTC."

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / mountOrigin / description

Previous value: -"Origin of the Next.js app serving it via @pagehub/next, e.g. \"https://app.example.com\". Needs publish_site static: true."New value: +"Origin of the Next.js app serving it via @pagehub/next, e.g. \"https://app.example.com\"."

Changed8 schema fields changedOct 19, 2026

changedInput schema / properties / blockAiCrawlers / description

Previous value: -"true blocks known AI crawlers in robots.txt and turns off /llms.txt. Search engines unaffected."New value: +"true blocks AI crawlers in robots.txt and turns off /llms.txt; search engines unaffected."

changedInput schema / properties / crawlMode / description

Previous value: -"public = indexed. noindex = viewable by link, kept out of search (use for a client copy not yet on its own domain). private_preview = noindex + robots.txt Disallow."New value: +"public = indexed. noindex = viewable by link, kept out of search (a client copy not yet on its domain). private_preview = noindex + robots.txt Disallow."

changedInput schema / properties / description / description

Previous value: -"Site-wide fallback meta description."New value: +"Fallback meta description."

addedInput schema / properties / language

Added value: +{
+  "description": "<html lang> tag: \"uk\", \"pt-BR\"… \"\" = en.",
+  "maxLength": 35,
+  "type": "string"
+}

changedInput schema / properties / mountOrigin / description

Previous value: -"Origin of the Next.js app serving this site via @pagehub/next, e.g. \"https://app.example.com\". Needs publish_site static: true."New value: +"Origin of the Next.js app serving it via @pagehub/next, e.g. \"https://app.example.com\". Needs publish_site static: true."

changedInput schema / properties / rotateMountKey / description

Previous value: -"true issues a new mount key (returned once) and invalidates the old one."New value: +"true issues a new mount key (shown once), voiding the old one."

changedInput schema / properties / timezone / description

Previous value: -"IANA timezone for form notification emails, e.g. \"America/Los_Angeles\". Empty string = UTC."New value: +"IANA zone for notification emails, e.g. \"America/Los_Angeles\". \"\" = UTC."

changedInput schema / properties / title / description

Previous value: -"Site-wide fallback <title>."New value: +"Fallback <title>."

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

Changed2 schema fields changedOct 5, 2026

addedInput schema / properties / crawlMode

Added value: +{
+  "description": "public = indexed. noindex = viewable by link, kept out of search (use for a client copy not yet on its own domain). private_preview = noindex + robots.txt Disallow.",
+  "enum": [
+    "public",
+    "noindex",
+    "private_preview"
+  ],
+  "type": "string"
+}

addedInput schema / properties / ogImage

Added value: +{
+  "description": "https URL, 1200×630.",
+  "maxLength": 2048,
+  "type": "string"
+}

Changed4 schema fields changedOct 4, 2026

changedInput schema / properties / blockAiCrawlers / description

Previous value: -"true adds a robots.txt Disallow for known AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, …) and turns off /llms.txt + /llms-full.txt. Search engines are unaffected. Off also means AI assistants can read the site to answer questions or book on the visitor's behalf. Takes effect immediately, no publish needed."New value: +"true blocks known AI crawlers in robots.txt and turns off /llms.txt. Search engines unaffected."

changedInput schema / properties / mountOrigin / description

Previous value: -"Origin of your own Next.js app when it serves this site at its root through @pagehub/next, e.g. \"https://app.example.com\" — https, no path or trailing slash. Canonical URLs, og:url and the sitemap then use that origin, and the page's form, analytics and favicon calls go through the app's /_pagehub/ path. The site must have static delivery on (publish_site static: true). Setting it issues a mount key (returned once) that the app must send so PageHub sees each visitor's real IP; clearing it removes the key. Empty string clears it. Takes effect immediately, no publish needed."New value: +"Origin of the Next.js app serving this site via @pagehub/next, e.g. \"https://app.example.com\". Needs publish_site static: true."

changedInput schema / properties / rotateMountKey / description

Previous value: -"true issues a new mount key and invalidates the old one (the site must have a mountOrigin). The new key is returned once — set it as PAGEHUB_MOUNT_KEY in the host app, or that app's visitors share one IP for rate limits and analytics until you do."New value: +"true issues a new mount key (returned once) and invalidates the old one."

changedInput schema / properties / timezone / description

Previous value: -"The business's IANA timezone, e.g. \"America/Los_Angeles\". Times in the site's form notification emails are shown in it; empty string clears it (UTC). Takes effect immediately, no publish needed."New value: +"IANA timezone for form notification emails, e.g. \"America/Los_Angeles\". Empty string = UTC."

Changed2 schema fields changedOct 4, 2026

addedInput schema / properties / mountOrigin

Added value: +{
+  "description": "Origin of your own Next.js app when it serves this site at its root through @pagehub/next, e.g. \"https://app.example.com\" — https, no path or trailing slash. Canonical URLs, og:url and the sitemap then use that origin, and the page's form, analytics and favicon calls go through the app's /_pagehub/ path. The site must have static delivery on (publish_site static: true). Setting it issues a mount key (returned once) that the app must send so PageHub sees each visitor's real IP; clearing it removes the key. Empty string clears it. Takes effect immediately, no publish needed.",
+  "maxLength": 256,
+  "type": "string"
+}

addedInput schema / properties / rotateMountKey

Added value: +{
+  "description": "true issues a new mount key and invalidates the old one (the site must have a mountOrigin). The new key is returned once — set it as PAGEHUB_MOUNT_KEY in the host app, or that app's visitors share one IP for rate limits and analytics until you do.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / timezone

Added value: +{
+  "description": "The business's IANA timezone, e.g. \"America/Los_Angeles\". Times in the site's form notification emails are shown in it; empty string clears it (UTC). Takes effect immediately, no publish needed.",
+  "maxLength": 64,
+  "type": "string"
+}

Changed1 schema field changedSep 30, 2026

addedInput schema / properties / blockAiCrawlers

Added value: +{
+  "description": "true adds a robots.txt Disallow for known AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, …) and turns off /llms.txt + /llms-full.txt. Search engines are unaffected. Off also means AI assistants can read the site to answer questions or book on the visitor's behalf. Takes effect immediately, no publish needed.",
+  "type": "boolean"
+}

First observedSep 28, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Adds behavior beyond the annotations: changes take effect immediately without a publish step, and "" clears a field — a useful confirmation of the destructiveHint=true profile. It also explains the fallback semantics of title/description/og*. It does not spell out the consequence of rotating the mount key (the schema does), so it stops short of 5.

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?

Dense and front-loaded: the field list comes first, then the two key behavioral rules, then a pointer to the reference tool. Telegraphic phrasing ('"" clears') is efficient rather than sloppy, though the middle clauses are packed tightly.

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?

With 12 parameters, no output schema, and annotations already declaring the mutation profile, the description covers the critical surprises (immediacy, clearing, fallbacks). It never states that a site id is needed to target the record, which is a notable gap given the schema marks zero required parameters.

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. The description does add meaning the schema doesn't fully convey — that title/description/og* act as fallbacks for pages lacking their own SEO, and that an empty string clears rather than sets — but most parameters are still only explained in the schema.

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?

Specific verb ('Set') plus an enumerated list of the site-level fields it mutates, which separates it from page-level tools like update_page and from publish_site ('immediate, no publish'). The field list reads partly like a schema echo, but the resource and scope are unambiguous.

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?

'immediate, no publish' implies this is for pre-publish configuration changes, and it routes to get_style_reference({ topic: "site" }) for details, which is real routing value. However, no explicit when-not-to-use is given (e.g. vs. create_site or set_favicon/set_portal for individual settings), leaving the agent to infer boundaries.

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?