Skip to main content
Glama

Update site

update_site
Destructive

Update the site's name (URL slug), title, description, ogImage, search indexing, AI-crawler blocking, timezone or mount origin/key — immediate, no publish. title/description/ogImage are the fallback , description and og:image for pages without their own seo. Empty string clears. Details: get_style_reference({ topic: "site" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSite id.
nameNoURL slug (subdomain): lowercase letters, digits, hyphens.
titleNoSite-wide fallback <title>.
ogImageNohttps URL, 1200×630.
timezoneNoIANA timezone for form notification emails, e.g. "America/Los_Angeles". Empty string = UTC.
crawlModeNopublic = 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.
descriptionNoSite-wide fallback meta description.
mountOriginNoOrigin of the Next.js app serving this site via @pagehub/next, e.g. "https://app.example.com". Needs publish_site static: true.
rotateMountKeyNotrue issues a new mount key (returned once) and invalidates the old one.
blockAiCrawlersNotrue blocks known AI crawlers in robots.txt and turns off /llms.txt. Search engines unaffected.

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. Changed2 schema fields changed
    • 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"
      +}
  3. Changed4 schema fields changed
    • 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."
  4. Changed2 schema fields changed
    • 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"
      +}
  5. Changed1 schema field changed
    • 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"
      +}
  6. Changed1 schema field changed
    • 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"
      +}
  7. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely non-redundant behavior: changes are applied immediately with no publish step, an empty string clears a value, title/description/ogImage act as fallback SEO only for pages lacking their own, and mount key rotation is destructive to the previous key. It still doesn't say whether the update is partial/patch-style or what happens to omitted fields, which matters for a destructive, non-idempotent update.

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 verb and the field list, followed by two short clarifying sentences (fallback semantics, empty-string clearing) and a pointer to get_style_reference. It is dense but every clause carries information; the only mild cost is that the field enumeration makes the first sentence very long.

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 10-parameter, 0-required, no-output-schema mutation tool this is close to sufficient: it names the affected attributes, the clearing convention, immediate-effect behavior, and points to get_style_reference for detail. The remaining gap is that it never states the semantics of a partial update (unset fields left unchanged) nor the permissions/publish precondition for mountOrigin, which the agent would need to call confidently.

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 description coverage is 100%, so the baseline is 3, and the description legitimately earns above that: it explains the fallback semantics of title/description/ogImage (only used for pages without their own SEO), the 'empty string clears' convention, and glosses the crawl/indexing and AI-crawler options, which map to crawlMode and blockAiCrawlers. rotateMountKey's 'returned once' detail is left to the schema, so it isn't fully self-contained.

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?

States a specific verb (update) and resource (site) and enumerates the mutable fields so an agent knows exactly what this tool covers: name/slug, title, description, ogImage, indexing, AI-crawler blocking, timezone, mount origin/key. It doesn't explicitly contrast itself with the adjacent mutation tools (patch_site_bulk, patch_site_node, create_site), but the field enumeration makes its scope 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?

The clause 'immediate, no publish' tells the agent changes take effect without publish_site, which is useful selection context, and the get_style_reference({ topic: "site" }) pointer routes to further detail. However there is no explicit when-to-use/when-to-use-something-else guidance, and no statement of prerequisites such as needed permissions or the publish_site static: true dependency for mountOrigin (that only appears in the schema).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources