Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

common-get-item-clone

Read-only

Retrieve all clones for a specified Sitecore item by ID or path to identify where content is inherited or reused.

Instructions

Returns all the clones for the specified 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-get-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.
databaseNoDatabase to resolve an id against (default master).

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 already declare readOnlyHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not explain what a 'clone' represents, what is returned per item, or how it interacts with the related new/convert clone tools.

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 front-loaded sentence with no filler or redundancy. It is appropriately sized, though its brevity borders on under-specification rather than tightness.

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?

For a read-only tool with a fully documented schema and no output schema, the description is minimally adequate. It nonetheless omits the nature of a clone and any return-shape context, which would matter given the multiple clone-related siblings.

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 all five parameters (id, path, full, fields, database) are already well documented in the schema, including the id-or-path rule and the full-vs-fields interaction. The description adds no parameter meaning beyond that, which is the expected baseline when the schema carries the load.

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?

States a specific verb ('Returns') and resource ('all the clones for the specified item'), so the agent understands the read operation. However, it does not distinguish itself from the closely related siblings common-new-item-clone and common-convert-from-item-clone, leaving the clone-family boundary to be inferred.

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 offers no when-to-use guidance, prerequisites, or reference to alternatives. With sibling clone tools (new/convert) present, an agent gets no help choosing between them.

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