Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update block content

update_block_content
Destructive

Update a specific block's content on a page by merging changes or replacing the whole content. Use it to edit content and layout blocks, then correct and resave if block warnings appear.

Instructions

Update a specific block's content on a page. Defaults to merging with existing content; pass mode: 'replace' to overwrite the block's whole content. Works for content and 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 on the shared draft unless the page already stores that block - compose types that are not deployed yet in target: 'devDraft' and promote once the code ships; 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>",
      "blockId": "<blockId>",
      "content": "<content>"
    },
    "name": "update_block_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo'merge' (default) shallow-merges the given content per language into what's already there. 'replace' sets the block's entire content to exactly what you provide, dropping any language or field you don't include - use it to fix legacy/malformed content (e.g. a repeater stored as an object instead of an array).
pageIdYesPage id or slug
targetNo'draft' (default) edits the shared page draft. 'devDraft' edits YOUR per-user dev draft overlay (owned by the token's user; starts from the current page blocks when no overlay exists) - for block types not deployed yet; promote with promote_dev_draft.
blockIdYesBlock instance id (UUID) to update
contentYesContent keyed by language, e.g. { en: { title: 'New Title' } }. In 'merge' mode only the given fields change; in 'replace' mode this becomes the block's entire content. A relation field stores record id(s) from list_records - a single id string (hasOne) or an array of id strings (hasMany); the delivery API resolves them to records at render time. A relation field with mode 'all' stores no value.
settingsNo

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",
      +  "blockId",
      +  "content"
      +]
  2. First observedv0.73.1

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=true; the description explains exactly what that means (replace drops languages/fields not supplied) and adds the full behavioral envelope: blockWarnings on save, refusal of unregistered block types on the shared draft, and dev-draft overlay ownership. It discloses failure modes and remediation paths that no structured field carries.

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?

Purpose and merge/replace behavior are front-loaded, which is good. But the warnings section is one very long run-on sentence with stacked clauses and parentheticals that is hard to parse and repeats the 'type no longer registered' case twice.

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?

For a destructive, 6-parameter mutation with no output schema, the description covers the important ground: default vs. destructive mode, draft vs. dev draft, and what to do when blockWarnings come back. Minor omissions are the undocumented 'settings' parameter and no mention of permission or concurrency expectations.

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 already 83%, and the description mostly restates schema-documented behavior for mode and target rather than adding syntax or defaults beyond it. The 'settings' parameter goes unmentioned in both, and no parameter gets new semantics from the prose.

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?

States a specific verb and resource ('Update a specific block's content on a page') and adds scope detail — merge-by-default, replace on request, and that it covers both content and layout blocks. It does not distinguish itself from the sibling patch_block_content or update_page_blocks, so an agent must infer which updater to pick.

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 concrete selection rules: default merge vs. explicit mode 'replace', and use target 'devDraft' when composing block types not yet deployed. It also routes the agent to list_block_usage and list_block_types for remediation. It never states when to prefer the sibling patch_block_content instead, which is the main gap.

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