Skip to main content
Glama
Sign In
SitecoreMCP

SitecoreMCP

by ramseur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

common-remove-item-version-by-id

Remove specific versions of a Sitecore content item by ID, supporting language and version wildcards for bulk operations, with options to archive or delete recursively.

Instructions

Removes a version of a Sitecore item by ID.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe ID of the item to remove version for.
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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'Removes a version', implying a destructive mutation, but doesn't specify whether this is reversible, what permissions are required, or the consequences (e.g., data loss, recycling vs. permanent deletion). The description lacks critical behavioral context for a destructive operation.

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 with no wasted words. It's appropriately sized and front-loaded, clearly stating the core action without unnecessary elaboration.

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 complexity of a destructive mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It fails to address behavioral aspects like safety, permissions, or output format, leaving significant gaps for an AI agent to understand the tool's full context.

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 schema description coverage is 100%, with all 7 parameters well-documented in the input schema. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 ID'), making the purpose specific and understandable. However, it doesn't distinguish this tool from its sibling 'common-remove-item-version-by-path', which performs the same operation but uses a path instead of an ID for identification.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, permissions, or when to choose this over 'common-remove-item-version-by-path' or other deletion tools like 'common-remove-archive-item'. Usage is implied only by the tool name and parameters.

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