Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Promote dev draft

promote_dev_draft
Destructive

Promotes your per-user dev draft overlay onto a page's shared draft, replacing its blocks after composed block code is deployed. It refuses unsafe promotions that add warnings or empty content.

Instructions

Promote YOUR per-user dev draft overlay onto the page's shared draft (replaces the shared draft blocks; the overlay belongs to the token's user). Do this after the block code for the composed types is deployed to the site. Fails when you have no dev draft for the page. The promote is refused with DEV_DRAFT_PROMOTE_REFUSED when the dev draft introduces block warnings the shared draft does not already carry, or empties a language, the shared values or the flat content a shared-draft block holds, or leaves out a shared-draft block that holds content (it would be removed from the page); the error lists the blockWarnings and emptiedBlocks, where removed: true marks a left-out block. Fix the dev draft (update_page_blocks with target: 'devDraft') and promote again; pass force: true only after fixing is ruled out. Promoting a block whose type the workspace block manifest does not register is refused - run cmssy sync-manifest from the deployed code first.

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": "promote_dev_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoPromote even though the server refused it with DEV_DRAFT_PROMOTE_REFUSED. Use only after fixing the dev draft is ruled out - it overwrites the shared draft with the warnings and emptied blocks the refusal listed.
pageIdYesPage id or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Promote even though the server refused it with DEV_DRAFT_PROMOTE_REFUSED. Use only after fixing the dev draft is ruled out - it overwrites the shared draft with the warnings and emptied blocks the refusal listed.",
      +  "type": "boolean"
      +}
    • 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/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=true; the description goes well beyond by naming the exact refusal code (DEV_DRAFT_PROMOTE_REFUSED), enumerating the four refusal conditions, and describing the error payload (blockWarnings, emptiedBlocks, removed: true). That is substantial disclosure of destructive semantics and failure modes, though it does not state what a successful response returns.

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 side effect, and every clause carries operational information (prerequisites, refusal rules, error shape, recovery path). It is dense to the point of being one long run-on paragraph, which slightly hurts scannability but not content value.

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 operation with no output schema, the definition covers prerequisites, failure conditions, error payload interpretation, and recovery. The only gap is what a successful promotion returns, which the agent would otherwise have to discover empirically.

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 both parameters are already documented in structured form, giving a baseline of 3. The description still adds decision-relevant meaning for force: what it overrides, what it overwrites, and the condition under which it may be used.

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 the specific verb (promote), the precise resource (the caller's per-user dev draft overlay), and the target it lands on (the page's shared draft), including the side effect that shared draft blocks are replaced. This is far more specific than the title and distinguishes it from block-editing siblings such as update_page_blocks and add_block_to_page.

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 explicit ordering guidance ('Do this after the block code for the composed types is deployed'), a prerequisite command ('run cmssy sync-manifest from the deployed code first'), and a concrete recovery alternative (fix via update_page_blocks with target: 'devDraft'). It also constrains the escape hatch: pass force: true only after fixing is ruled out.

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