Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Remove block from page

remove_block_from_page
Destructive

Removes a specific content or layout block from a page by page ID or slug and block instance UUID. Use it to delete unwanted blocks from Cmssy pages.

Instructions

Remove a specific block from a page by its instance id. Works for content and layout blocks.

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>"
    },
    "name": "remove_block_from_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageIdYesPage id or slug
blockIdYesBlock instance id (UUID) to remove

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is an irreversible-style mutation. The description adds that both content and layout block types are supported, which is real behavioral context, but it says nothing about what happens to child/nested blocks, whether the page must be unpublished or locked, or whether the removal takes effect immediately.

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 short sentences, zero padding, with the identifying key framed up front and the scope note placed after. Nothing needs trimming and nothing is buried.

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 two-parameter destructive tool with full schema coverage, annotations supplying the safety profile, and no output schema, this is close to sufficient. The only real gap is the absence of any note on side effects such as orphaned child blocks or page-state prerequisites.

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 both parameters are documented, so baseline is 3. The phrase 'by its instance id' reinforces that blockId is an instance UUID rather than a block type id, a useful distinction, but the schema already says exactly that, so little is added.

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 (remove a block from a page) and the keying mechanism (instance id), plus a scope note that covers both content and layout blocks. It implicitly contrasts with add_block_to_page but never names a sibling, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the verb; there is no explicit when-to-use or when-not-to-use guidance and no alternative named (e.g., update_page_blocks or update_page_layout, which could also alter block composition). The 'works for content and layout blocks' line clarifies scope of applicability rather than directing tool selection.

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