Skip to main content
Glama

Remove Block

remove_block
Destructive

Remove a content block from a page.

Annotations: read-only=false, destructive=true, idempotent=false, open-world=false. Why: Deletes a section from the DRAFT — destructive. Not idempotent: legacy positional block handles can resolve to a different section on a repeat. Closed-world. The live site changes only when the user confirms publish_site; the draft stays editable in the Zarla editor.

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": {
      "site_id": "<site_id>",
      "page_slug": "<page_slug>",
      "block_id": "<block_id>"
    },
    "name": "remove_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYes
block_idYesBlock ID to remove
page_slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

The description goes beyond the annotations by supplying rationale: it explains that the deletion targets the DRAFT, that non-idempotency stems from legacy positional block handles potentially resolving to a different section on a repeat call, and that the live site is unaffected until publish_site is confirmed. That 'why' is genuine added value over the raw hint flags. It does not describe the response or what happens to a page left with zero blocks.

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 core purpose is front-loaded in one short sentence, followed by a clearly separated rationale block. The annotation restatement is somewhat redundant (the flags are already in structured fields), but the accompanying reasoning earns most of its space.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema, the draft-vs-live and non-idempotency caveats cover the most important behavioral risk. However, two of three parameters remain undocumented in both schema and description, and there is no statement about failure modes, such as an unresolvable block_id after a prior removal.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% — block_id is documented in the schema while site_id and page_slug have no descriptions anywhere. The description text adds no parameter-level meaning: no format for page_slug, no note that site_id is a UUID, and no explanation of the block handle semantics that it itself flags as a hazard.

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?

The first sentence gives a specific verb and resource ('Remove a content block from a page'), which distinguishes it from sibling remove_page and remove_logo by resource type. It stops short of explicitly naming or contrasting those siblings, but the resource noun alone is unambiguous.

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 implied rather than stated: the annotations paragraph explains that the removal affects the DRAFT and only reaches the live site after publish_site, which is useful context for when this tool's effect becomes visible. There is no explicit when-to-use/when-not guidance, no mention of preconditions such as obtaining a valid block_id via get_page, and no contrast with update_block or reorder_blocks.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.