Skip to main content
Glama
plone

Plone MCP Server

Official
by plone

Remove Single Block

plone_remove_single_block

Deletes a single block from a Plone content item using its path and block ID.

Instructions

Deletes a single block from a content item, identified by its block ID. Example: plone_remove_single_block({path: '/my-page', blockId: 'abc123'})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesPath to the content
blockIdYesID of the block to remove
Behavior2/5

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

Only states 'Deletes' with no additional behavioral context. No annotations provided, so description must carry burden; missing details on side effects, error handling, or reversible nature.

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?

Extremely concise: one sentence plus an example. No extraneous content, every part serves a purpose.

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?

Adequate for a simple two-param tool with no output schema. Covers core action, but lacks preconditions or error scenarios (e.g., what if block ID doesn't exist).

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?

Input schema covers both parameters with descriptions (100% coverage). The description adds an example usage that clarifies the expected format (leading slash in path, blockId as string), providing practical context beyond schema.

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?

Clearly states the tool deletes a single block from a content item, with specific identification via block ID. Distinguishes from sibling tools like plone_delete_content (whole content) and plone_update_single_block (modify).

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?

Implied usage for deleting a block, but no explicit when-to-use or alternatives. Lacks guidance on when not to use (e.g., when wanting to delete entire content).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/plone/plone-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server