Skip to main content
Glama

Switch Design

switch_design
Destructive

Move the site onto a marketplace design from list_designs. FULL REDESIGN: the design's colors, fonts, section layouts and section order come across on the home page AND every internal page, while the site's business details, words, photos, services, forms and pages stay. Sections the design has that the site has no content for are left out (nothing is invented); the site's own sections the design has no spot for are kept. A backup of the current site is saved automatically FIRST — the response reports it under "backup" (restorable via Site Backups in the Zarla editor); if backup.created is false with skipped_reason "snapshot_failed", warn the user the switch proceeded WITHOUT a backup. The response includes a "preview_url" for the updated draft — share THAT link, do not construct your own. Nothing changes on a live site until publish_site. For colors or fonts only, use update_design.

Annotations: read-only=false, destructive=true, idempotent=false, open-world=false. Why: Replaces the draft's design preset (content is kept) — non-additive, so destructive by the MCP definition. Not idempotent: a backup of the previous design is saved before every switch, so a repeat adds another backup row. 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>",
      "schema_key": "<schema_key>"
    },
    "name": "switch_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
schema_keyYesThe design's schema_key from list_designs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: exactly what transfers (colors, fonts, section layouts/order on home and internal pages) versus what is preserved (business details, words, photos, services, forms, pages), and how content/design mismatches are resolved. It also discloses the automatic backup, the 'backup.created is false / skipped_reason snapshot_failed' warning path, and that a repeat creates another backup row — details the annotations only summarize.

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-loads the action and the 'FULL REDESIGN' scope before the fine print, and each sentence carries operational value (backup warning, preview_url handling, publish boundary). It is dense with capitalization and parentheticals, which makes it slightly heavier to scan than necessary, but nothing is redundant.

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?

There is no output schema, and the description covers the return shape that matters: the 'backup' object, the 'preview_url' (with an instruction to share rather than construct it), and the failure indicator. Nothing an agent needs in order to call it safely or report results is missing.

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 coverage is 50%: schema_key is described in the schema itself and the description only restates where it comes from (list_designs). site_id is never explicitly explained in the description, though the surrounding narrative makes it clear the target site is the draft being redesigned. Adequate but not compensating fully for the uncovered parameter.

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 ('Move the site onto a marketplace design from list_designs') and immediately qualifies scope with 'FULL REDESIGN'. It distinguishes itself from update_design in the final sentence, so an agent can route between them without opening schemas.

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?

Gives an explicit exclusion and alternative: 'For colors or fonts only, use update_design', plus 'Nothing changes on a live site until publish_site', which tells the agent the follow-up step. The prerequisite that the design comes from list_designs is also stated.

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.