Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update region settings

update_region_settings
Destructive

Set one page layout region's settings, such as sidebar width or header variant, with manifest validation and a single version-guarded write that leaves other regions unchanged.

Instructions

Set the settings of one layout region on a page, e.g. a sidebar's width or a header's variant. Reads the page's current region settings, replaces only the named region and writes the whole list back (page.updateLayout with layoutRegionSettings, one version-guarded write); entries for regions or keys the manifest no longer declares are pruned on the way. Values are validated against the workspace layout manifest's region settings schema: an unknown region, an unknown key, or non-empty values on a region that declares no settings (such a region accepts {} only) is rejected with the backend's BAD_USER_INPUT message. Child pages inherit the region's settings unless they set their own (see get_page.resolvedRegions).

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>",
      "region": "<region>",
      "values": "<values>"
    },
    "name": "update_region_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesThe page id (from list_pages/get_page)
regionYesLayout region name declared by the workspace's layout manifest, e.g. 'sidebar' or 'header'
valuesYesSettings values for the region, keyed as the manifest's region settings schema declares. Replaces this region's values; other regions keep theirs. A region that declares no settings accepts {} only.
expectedVersionNoOptimistic-concurrency guard. Defaults to the version read before the write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "pageId",
      +  "region",
      +  "values"
      +]
  2. First observedv0.73.1

TDQS

A4.6/5.0
Behavior5/5

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

Well beyond the annotations, it discloses the read-modify-write cycle, that the entire list is written back in one version-guarded page.updateLayout call, and that entries for regions or keys no longer declared in the manifest are pruned on the way — a real behavioral consequence of a destructiveHint=true tool. It also spells out the validation behavior and the exact BAD_USER_INPUT failure modes (unknown region, unknown key, non-empty values on a settingless region).

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?

The purpose is front-loaded and every clause carries information (pruning, validation, inheritance) rather than filler. It is dense to the point of being a single long run-on sentence midsection, which slightly hurts scannability, but nothing is genuinely wasted.

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 mutation tool with no output schema and nested object values, the description covers the write mechanics, the destructive side effect, validation failure modes, concurrency guarding, and inheritance behavior. An agent has everything it needs to call this safely without guessing.

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 is 3; the description adds value by explaining that region names and value keys must be declared by the workspace manifest and that a settingless region accepts {} only, plus the child-page inheritance semantics that the schema never mentions. The expectedVersion behavior is already covered by the schema, so it isn't re-explained here.

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?

The description opens with a precise verb and a tightly scoped resource: 'Set the settings of one layout region on a page', and immediately anchors it with concrete examples ('a sidebar's width or a header's variant'). The 'one region' scope implicitly separates it from whole-layout siblings like update_page_layout or update_page_settings.

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 clearly conveys the context in which the tool applies (per-region edits, region names must come from the layout manifest) and points to get_page.resolvedRegions for the inheritance case. It stops short of explicitly naming an alternative tool for whole-layout changes or excluding cases, so a 4 rather than a 5.

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