Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update page layout

update_page_layout
Destructive

Update a page's layout by setting parent inheritance, applying region overrides, or replacing all layout blocks; use it to adjust page structure and resolve block manifest warnings.

Instructions

Update page-level layout: inheritance, overrides, or replace all layout blocks. If the result includes blockWarnings, the saved content violates the workspace block manifest (unknown field, wrong value shape, or a stored block whose type is no longer registered) - correct the content and save again, unless the warning is about a stored block whose type is no longer registered: that one is a manifest problem, so restore or sync the type, or find the block with list_block_usage and migrate or remove it. When the warnings also say when the workspace block manifest was last synced, the field or type may simply be newer than the manifest: if the site's code declares it, keep the content and sync the manifest (cmssy sync-manifest in the site's repo) instead. A block whose type the workspace block manifest does not register is refused unless the page already stores that block - pick registered types from list_block_types.

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": {
      "pageId": "<pageId>"
    },
    "name": "update_page_layout"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug
layoutBlocksNoFull replacement array of layout blocks (each must have 'type')
inheritsLayoutNoWhether this page inherits layout from its parent
layoutOverridesNoLayout overrides for inherited regions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / pageId / description
      Previous value: -"Page id"New value: +"Page id or slug"
    • addedInput schema / required
      Added value: +[
      +  "pageId"
      +]
  2. First observedv0.73.1

TDQS

A4/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses real behavior: layoutBlocks is a full replacement, and an unregistered block type is refused unless the page already stores that block. It also explains the blockWarnings return signal, its three causes, and the remediation path for each, which is substantial disclosure absent from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in one sentence, but the remainder is a dense multi-clause conditional chain that partially restates itself ('correct the content and save again, unless the warning is about... that one is a manifest problem'). The embedded shell command and layered dashes make it harder to scan than necessary.

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 no output schema, the description appropriately covers the blockWarnings return value and its handling, plus the refusal rule for unregistered types. It omits prerequisites such as page lock requirements (a take_over_page_lock sibling exists) and what happens to existing overrides when inheritance changes.

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 100%, so pageId, layoutBlocks, inheritsLayout and layoutOverrides are already documented, including the 'each must have type' constraint. The description only adds the type-registration constraint on blocks, which is useful but does not deepen per-parameter syntax or interaction semantics (e.g. how layoutOverrides interacts with inheritsLayout).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence names a specific verb and resource and enumerates the three modes of operation (inheritance, overrides, full block replacement), which lets an agent understand scope immediately. It does not explicitly distinguish itself from the close sibling update_page_blocks, leaving ambiguity about which tool performs partial block edits versus whole-layout replacement.

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 conditional guidance: correct content and re-save on blockWarnings, use list_block_usage to find and migrate an unregistered stored block, or sync the manifest when the field/type is newer than the manifest, and pick types from list_block_types. It stops short of stating when to choose this tool over update_page_blocks or update_page_settings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools