Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

common-convert-from-item-clone

Convert a Sitecore clone into an independent item so it no longer inherits source changes; optionally recurse the branch.

Instructions

Converts an item from a clone to a fully independent item.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "common-convert-from-item-clone"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the item to be analysed for clones presence. Supply this or path.
fullNoReturn the unprojected .NET object graph. Very large (100,000+ chars/item); diagnostics only.
pathNoThe path of the item to be analysed for clones presence. Supply this or id.
fieldsNoExtra Sitecore field names to include, e.g. ['Title']. Ignored when full is true.
recurseNoConverts the whole branch rather than a single item.
databaseNoDatabase to resolve an id against (default master).
passThruNoReturns the item that was converted from a clone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the description need not restate safety, but it still leaves key behavior unexplained: whether the clone link is severed permanently, whether the conversion is reversible, and what permissions are required. No contradiction with annotations, but no added behavioral context either.

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?

A single tight sentence with no filler and a front-loaded verb. It is efficient, though the brevity comes at the cost of the missing context noted elsewhere.

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?

Schema coverage is full and annotations exist, so the structured fields carry most of the load, and there is no output schema to explain. Still, the description does not address the notable `recurse` branch-wide effect or the irreversible-looking nature of the conversion, which an agent should know before invoking a mutation.

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%, so the schema already documents all seven parameters. The description adds no parameter-level meaning beyond the schema, which is the baseline 3 case.

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 states a specific verb (converts) and resource (an item from a clone), and the outcome (fully independent item) is unambiguous. It does not explicitly contrast itself with the adjacent clone tools (common-new-item-clone, common-get-item-clone), so it stops short of a 5.

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, no mention of prerequisites, and no routing to siblings such as common-new-item-clone. The agent must infer usage entirely from the one-line purpose.

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