Skip to main content
Glama
Sign In
SitecoreMCP

SitecoreMCP

by ramseur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

common-remove-item-version-by-path

Remove specific language versions of Sitecore items by path, supporting wildcards for bulk deletion and recursive child item processing.

Instructions

Removes a version of a Sitecore item by path.

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": {
      "path": "<path>",
      "language": "<language>"
    },
    "name": "common-remove-item-version-by-path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe path of the item to remove version for (e.g. /sitecore/content/Home).
languageYesLanguage that should be deleted form the provided item. Language parameter supports globbing so you can delete whole language groups using wildcards.
versionNoVersion that should be deleted form the provided item. Version parameter supports globbing so you can delete whole version groups using wildcards.
recurseNoRemoves language versions from the item and all of its children.
maxRecentVersionsNoTrims the selected language to value specified by this parameter.
databaseNoThe database containing the item (defaults to the context database).
archiveNoMoves the items to the archive rather than recycle bin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states 'Removes a version,' implying a destructive mutation, but doesn't clarify critical aspects like whether this operation is reversible, what permissions are needed, or the impact on related items. The description lacks details on error conditions, rate limits, or confirmation prompts, which are essential for a destructive tool.

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?

The description is a single, direct sentence that efficiently conveys the core action without unnecessary words. It's front-loaded with the main purpose, making it highly concise and well-structured for quick understanding.

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?

Given the tool's complexity (7 parameters, destructive operation) and lack of annotations and output schema, the description is insufficient. It doesn't explain the return values, error handling, or behavioral nuances like the effects of 'archive' or 'recurse' parameters, leaving significant gaps for an agent to operate safely and effectively.

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?

The input schema has 100% description coverage, providing detailed explanations for all 7 parameters (e.g., path, language with globbing, recurse). The description adds no additional parameter semantics beyond what the schema already documents, so it meets the baseline of 3 for high schema coverage without extra value.

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 description clearly states the verb ('Removes') and resource ('a version of a Sitecore item by path'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'common-remove-item-version-by-id' (which appears in the list), which would require mentioning the path-based approach versus ID-based alternative.

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?

The description provides no guidance on when to use this tool versus alternatives like 'common-remove-item-version-by-id' or other deletion tools in the sibling list. It also doesn't mention prerequisites, such as required permissions or database context, leaving the agent without usage context.

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