Concrete CMS MCP Server

delete-page-version-by-page-id-and-version-id

Destructive

Deletes a specific page version in Concrete CMS using its page ID and version ID, removing outdated revisions from a page's version history.

Instructions

Delete a page version.

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>",
      "versionID": "<versionID>"
    },
    "name": "delete-page-version-by-page-id-and-version-id"
  }
}

Input Schema

Name	Required	Description	Default
`pageID`	Yes	ID of page
`versionID`	Yes	versionID parameter

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0-alpha.1Aug 11, 2026

TDQS

C2.6/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the irreversible nature is known structurally. The description adds nothing beyond that: it does not say whether the deletion is permanent, whether prior versions become restorable, what permissions are required, or what happens on an invalid/unknown version ID. With annotations covering the safety profile, this thin addition warrants a 2.

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?

It is a single, front-loaded sentence with zero padding, which is structurally clean. The brevity is arguably excessive for a destructive operation, but there is no wasted wording to penalize.

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

Completeness2/5

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

This is a destructive mutation with no output schema and no annotations beyond the safety hints, so the description must carry information about consequences and preconditions. It supplies none — no confirmation of permanence, recoverability, or error behavior — leaving an agent unable to predict the effect of the call.

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 description coverage is 100% and both required path parameters (pageID, versionID) are documented in the schema, so the schema carries the parameter burden. The description contributes no extra semantics about path placement, ID provenance, or scope — baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Delete a page version'), so an agent knows the operation type. However, it is essentially a de-hyphenated restatement of the tool name and the annotation title, and it gives no differentiation from nearby siblings such as delete-page-by-id nor any indication of which version is targeted beyond the ID parameters.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance at all. The description does not mention that an alternative exists for updating a version (update-page-version-by-page-id-and-version-id) or for deleting an entire page, nor does it state any precondition, such as fetching the version first with the get counterpart.

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