Skip to main content
Glama

PageHub

by dev.pagehub
OverviewDiscussionsAdmin

Set theme

set_theme
DestructiveIdempotent

Write the site theme — preset, palette, darkPalette, styleGuide tokens, fonts, JSON-LD, site animations — into the draft, effective immediately. suggest_palettes / suggest_font_pairings only show options. ROOT company vars: patch_site_node. Palette names, styleGuide keys, workflow: get_style_reference({ topic: "theme" }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoSite id.
demoNoDemo URL.
fontsNoHint ({ url } or { families }) parsed into heading/body families when styleGuide omits them.
titleNoTitle.
hiddenNoHide from the public gallery.
jsonLdNoSchema.org JSON-LD object; {{company.*}} variables work inside it.
presetNoPreset slug; loads palette, fonts and styleGuide. Explicit params override it.
paletteNoComplete palette — replaces the existing one. [{ name, color }] with DaisyUI names (Primary, Primary Content, Secondary, Accent, Neutral, Base 100/200/300, Base Content, …), never "Background"/"Foreground". Colors: hex, rgb, hsl or oklch().
homePageNoHome page flag (default true).
animationsNoUpserted by key into theme.animations; nodes then use root.animation "site:<key>". Only for motion no built-in preset covers. Rules + examples: get_style_reference({ topic: "animation" }).
buildStyleNoVibe override for block filtering. Rarely needed — preset sets it.
styleGuideNoDesign tokens, merged into the existing styleGuide; each key becomes a CSS var (headingFontFamily, bodyFontFamily, radiusBox, buttonPadding, contentWidth, input*Color, …). Key list: get_style_reference({ topic: "theme" }).
darkPaletteNoOptional dark-mode palette with the same names. Enables dark mode.
descriptionNoShort description (≤75 chars).
removeAnimationsNoKeys to delete from theme.animations.

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 / animations
      Added value: +{
+  "description": "Upserted by key into theme.animations; nodes then use root.animation \"site:<key>\". Only for motion no built-in preset covers. Rules + examples: get_style_reference({ topic: \"animation\" }).",
+  "items": {
+    "properties": {
+      "direction": {
+        "enum": [
+          "normal",
+          "reverse",
+          "alternate",
+          "alternate-reverse"
+        ],
+        "type": "string"
+      },
+      "duration": {
+        "description": "Seconds, 0.05–30.",
+        "type": "number"
+      },
+      "easing": {
+        "description": "easeOut | easeIn | easeInOut | linear | spring | cubic-bezier() | steps()",
+        "maxLength": 80,
+        "type": "string"
+      },
+      "iterations": {
+        "description": "\"1\"–\"20\" or \"infinite\".",
+        "maxLength": 8,
+        "type": "string"
+      },
+      "key": {
+        "description": "Slug /^[a-z][a-z0-9-]{0,39}$/, no \"site:\" prefix.",
+        "maxLength": 40,
+        "type": "string"
+      },
+      "keyframes": {
+        "description": "Stops incl. at 0 and at 100.",
+        "items": {
+          "properties": {
+            "at": {
+              "description": "Percent, 0–100.",
+              "type": "number"
+            },
+            "style": {
+              "description": "Kebab-case CSS property → value, e.g. { \"clip-path\": \"inset(0 100% 0 0)\" }.",
+              "type": "object"
+            }
+          },
+          "required": [
+            "at",
+            "style"
+          ],
+          "type": "object"
+        },
+        "maxItems": 12,
+        "minItems": 2,
+        "type": "array"
+      },
+      "label": {
+        "maxLength": 60,
+        "type": "string"
+      },
+      "trigger": {
+        "enum": [
+          "scroll",
+          "load",
+          "continuous"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "key",
+      "label",
+      "trigger",
+      "duration",
+      "easing",
+      "iterations",
+      "keyframes"
+    ],
+    "type": "object"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • addedInput schema / properties / removeAnimations
      Added value: +{
+  "description": "Keys to delete from theme.animations.",
+  "items": {
+    "maxLength": 45,
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
  3. Changed1 schema field changed
    • removedInput schema / properties / image
      Removed value: -{
-  "description": "Preview image URL.",
-  "maxLength": 2048,
-  "type": "string"
-}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false, so the mutation/idempotency profile is covered. The description adds genuine context beyond them: changes land in the draft but take effect immediately, and (via schema-adjacent wording) palette replaces while animations upsert by key. Auth/permission requirements are not mentioned, but nothing contradicts the annotations.

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?

Front-loads the write action and scope in the first clause, then spends the remaining short sentences entirely on routing and reference pointers. No filler; each clause points at a decision the agent has to make.

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 15-parameter, nested, no-output-schema mutation tool, the description covers the risky areas: draft scoping, palette replacement, animation upserting, and where to find valid names/keys. It could say more about how partial updates interact (immediate effect on an unpublished draft vs published site), but nothing essential to calling it correctly is missing.

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 meaning the schema does not: valid palette names and styleGuide keys come from get_style_reference({ topic: "theme" }), ROOT company variables must go through patch_site_node, and animations are keyed/upserted. These pointers reduce misuse of the 15-parameter surface.

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 and resource ("Write the site theme") and enumerates exactly what it covers — preset, palette, darkPalette, styleGuide tokens, fonts, JSON-LD, animations — into the draft. It explicitly distinguishes itself from suggest_palettes / suggest_font_pairings, so an agent can separate it from siblings without opening either schema.

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 the adjacent tools and the boundary: suggest_* only show options, ROOT `company` vars belong to patch_site_node, and lookups go to get_style_reference({ topic: "theme" }). It gives clear routing context but does not state outright when this tool should be avoided (e.g. per-node styling instead of site-wide).

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