Skip to main content
Glama

Pagetool

Repaint a site's theme

set_theme
Idempotent

Repaints the palette and fonts of an existing site across every section without touching its content or structure - the tool for make it warmer, darker, more corporate. At least one of palette_primary, palette_neutral, font_heading, font_body is required. Free, and no account is needed for a draft you created.

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": "set_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
stageNotrue = work on a staged copy instead of the live site: preview it at staged_preview_url, then publish_staged or discard_staged. Omit for a normal (immediately live) edit.
site_keyNoThe site to theme. Defaults to the caller's current draft site when omitted.
font_bodyNoNew body font family name.
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.
favicon_urlNoThe browser-tab icon for the site: an https:// image URL (or a /path on the site), max 500 characters. May be the only field. Without one, customer domains show the first letter of the site name on its primary colour.
font_headingNoNew heading font family name.
palette_neutralNoNew neutral text/background colour as a #rrggbb hex string.
palette_primaryNoNew primary brand colour as a #rrggbb hex string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare idempotent=true and destructiveHint=false, so the description does not need to re-establish safety. It does add value beyond them: the guarantee that content and structure are untouched, the cost statement ("Free"), and the auth note that no account is needed for an anonymous draft. These are real behavioral facts not present in structured fields.

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?

Two dense sentences, front-loaded with the action and scope, followed by the requirement and cost/auth caveats. Minor cost: the phrase "the tool for make it warmer" is grammatically awkward and the favicon-only case goes unmentioned.

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 8 fully documented parameters, annotations, and no output schema, the remaining burden is small and the description covers purpose, minimum-input constraint, and cost/auth. It omits any mention of the stage/staged-preview path and the standalone favicon_url case, both of which live only in the schema.

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 would be 3. The description earns more by stating that at least one of palette_primary, palette_neutral, font_heading, or font_body is required — a cross-field constraint the schema's empty required array does not convey.

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?

"Repaints the palette and fonts of an existing site across every section without touching its content or structure" names a specific verb and resource plus a precise scope boundary. The content/structure exclusion implicitly separates it from edit_section and other section tools, so an agent can route correctly without opening a 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?

It gives concrete when-to-use framing ("make it warmer, darker, more corporate") and a hard prerequisite that at least one of the four styling fields be supplied. It stops short of explicitly naming alternatives such as edit_section for content changes or the stage/publish_staged flow, but the intended context is clear.

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