Skip to main content
Glama

Update a site

update_site
Destructive

Saves a new draft of an existing site. Send the whole site as get_site returned it, with your changes: each block with its id and its props whole, items and images included: a field left out takes its default and an image left out is removed. A block with a new id is added, and a block left out is deleted, with no undo in the editor, so send every block back. stickers go back whole too; [] removes the layer. websiteBgColor, websiteBgImage and fontFamily left out stay as they are; null removes one. Set image fields using URLs the upload card reported or list_images returned for this site. Nothing is saved if the site changed since that revision or anything is invalid. The owner publishes the draft in the editor. A new site name applies right away but only renames the site in Stick: the published page's title is set under SEO.

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": {
      "themeId": "<themeId>",
      "blocks": "<blocks>",
      "stickers": "<stickers>",
      "siteId": "<siteId>",
      "revision": "<revision>",
      "name": "<name>"
    },
    "name": "update_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesnull keeps the current name
blocksYesTop to bottom
siteIdYes
themeIdYes
revisionYesThe revision get_site returned
stickersYesThe decorative GIPHY sticker layer; [] for none.
editorUrlNoAs get_site returned it; ignored
fontFamilyNo
websiteBgColorNo
websiteBgImageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the destructiveHint/openWorldHint annotations: omitted blocks are deleted with 'no undo in the editor', omitted fields revert to defaults, omitted images are removed, nulls clear background/font fields, and the whole write fails on revision conflict or validation error. That is exactly the mutation risk detail an agent needs.

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 core action and dense with relevant detail, with no filler. The colon-chained sentences are long and could be split for scanability, 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?

For a destructive, non-idempotent 10-parameter mutation with no output schema, the description covers the full replace semantics, concurrency guard, failure behavior, and the publish handoff. An agent has everything needed to call it correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Several parameters lack schema descriptions (websiteBgColor, websiteBgImage, fontFamily), and the description supplies their partial-update contract: omitted keeps the value, null clears it. It also explains stickers-as-whole-layer with [] removing it, the new-id-adds / missing-id-deletes rule for blocks, and that editorUrl is ignored.

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 ('Saves a new draft of an existing site'), and the word 'existing' implicitly separates it from create_site while the mention of get_site's revision ties it to the read sibling. An agent can identify the operation without opening the 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?

Gives clear operating context: send the whole site as get_site returned it, use image URLs from the upload card or list_images, and the owner publishes afterwards. It does not explicitly exclude create_site for brand-new sites, but the 'existing site' framing and prerequisite revision supply a usable when-to-use rule.

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