Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Take over page lock

take_over_page_lock
Destructive

Take over a page's edit lock from another editor so subsequent publish or block updates are not refused with PAGE_LOCKED; the prior holder becomes read-only.

Instructions

Take over the edit lock on a page another editor is holding open, so the next write (publish_page, update_page_blocks, update_page_layout, ...) is not refused with PAGE_LOCKED. The previous holder is bounced to read-only and may lose unsaved work. Needs pages:edit or pages:publish on the page.

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

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug whose edit lock to take over

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 whose edit lock to take over"New value: +"Page id or slug whose edit lock to take over"
    • addedInput schema / required
      Added value: +[
      +  "pageId"
      +]
  2. First observedv0.73.1

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by disclosing the concrete consequence: the previous holder is bounced to read-only and may lose unsaved work. It also names the required scopes (pages:edit or pages:publish), which annotations do not cover.

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

Conciseness5/5

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

Two dense sentences, front-loaded with the action and its purpose, then the consequence and permission requirement. No wasted wording.

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 single-parameter mutation tool with no output schema, the description covers purpose, the failure mode it prevents, the side effect on the other editor, and the required permissions — everything an agent needs to decide and call correctly.

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% and the single pageId parameter is fully documented in the schema, so the description adds little parameter-level detail beyond the phrase 'on the page'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('take over the edit lock on a page') and immediately distinguishes itself from the write siblings (publish_page, update_page_blocks, update_page_layout) by explaining it exists to prevent PAGE_LOCKED refusals from those tools.

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 a clear triggering condition: use it when another editor holds the lock and the next write would be refused with PAGE_LOCKED. It does not explicitly state when not to use it (e.g. when you already hold the lock), but the context is strong enough to select it confidently.

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