Skip to main content
Glama

Update Design

update_design
DestructiveIdempotent

Update the visual design — colors, fonts, mood, density. Changes only the tokens you pass and touches nothing else (a contrast pass keeps text readable against a new scheme). To move the whole site onto a different marketplace design — layouts, palette and typography, with the site's content kept — use switch_design instead; this tool never changes layouts. The response includes a "preview_url" for the updated draft — share THAT link with the user, do not construct your own.

Annotations: read-only=false, destructive=true, idempotent=true, open-world=false. Why: Overwrites the draft's colours, fonts and design settings — non-additive, so destructive by the MCP definition; idempotent; closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site_id": "<site_id>"
    },
    "name": "update_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNo
densityNo
site_idYes
body_fontNoGoogle Fonts name
accent_colorNoHex color
heading_fontNoGoogle Fonts name
primary_colorNoHex color (e.g. "#1a1a2e")
background_colorNoHex color

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing partial-update semantics ('changes only the tokens you pass and touches nothing else'), an automatic contrast pass that keeps text readable, and the presence of a preview_url in the response with an explicit instruction to surface that link rather than fabricate one. That return-value guidance is not derivable from any structured field, and it is consistent with destructive=true and idempotent=true.

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-loaded with the core action, then the sibling routing, then the return-value instruction — the order an agent needs it. Every clause carries information (scope, contrast side effect, preview link) and there is no restatement of the title or padding.

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 an eight-parameter, non-read-only mutation tool with no output schema, the description covers scope, partial-update behavior, side effects, the alternate tool, and the key field of the untyped response. Nothing an agent needs to call it correctly and report results 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?

The description clusters the eight parameters into meaningful families (colors, fonts, mood, density) and the 'only the tokens you pass' line communicates that all of them are optional partial updates, which is real value beyond the schema. It does not explain the mood/density enum choices or font-name validity, so the two enum params still rely on their bare value lists.

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?

Names a specific verb plus resource ('Update the visual design') and enumerates the exact dimensions managed — colors, fonts, mood, density. It also states the inverse scope ('this tool never changes layouts'), which cleanly separates it from switch_design without requiring the agent to open 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use switch_design when moving the whole site onto a marketplace design with layouts and content preserved, use this tool otherwise. The exclusion ('never changes layouts') reinforces the boundary so there is no ambiguity about which sibling to pick.

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.