Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

authoring-copy-item

Copy a Sitecore item or its full subtree to another parent through the Authoring API; specify source by ID or path and destination by parent ID or path.

Instructions

Copies a Sitecore item to another parent over the Authoring and Management API. Copies the whole subtree by default; set deepCopy false to copy the item alone. Supply exactly one of id or path for the source, and exactly one of targetParentId or targetParentPath for the destination.

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": "authoring-copy-item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe source item's GUID. Supply this or path.
pathNoThe source item's full path. Supply this or id.
databaseNoThe database holding the item. Defaults to master.
deepCopyNoWhen false, copy only the item itself. Defaults to true (the whole subtree).
copyItemNameNoThe name for the copy. Defaults to Sitecore's own 'Copy of ...' naming.
targetParentIdNoThe GUID of the parent to copy into. Supply this or targetParentPath.
targetParentPathNoThe path of the parent to copy into. Supply this or targetParentId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare non-read-only and non-destructive, and the description adds meaningful behavior beyond them: subtree copying is the default, deepCopy=false narrows it to the single item, and the copy adopts Sitecore's 'Copy of ...' naming unless overridden. It omits anything about naming collisions or what the new item is named in the response, but the scope disclosure is solid.

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?

Three sentences, front-loaded with purpose and then constraints, with no padding or duplicated schema content.

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

Completeness4/5

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

Covers source, destination, subtree scope, naming default, and database default — enough to invoke correctly for a 7-parameter tool with no output schema. It could say whether the new item's identifier is returned, but that is a minor gap given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds the mutual-exclusivity contract between id/path and targetParentId/targetParentPath that the schema only implies with 'Supply this or ...'. It restates deepCopy's default, which is already in the schema, so it does not go far beyond the baseline.

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

Purpose5/5

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

States a specific verb ('Copies') and resource ('a Sitecore item to another parent') plus the API surface used, which cleanly separates it from authoring-move-item, authoring-create-item, and common-new-item-clone without opening any schema.

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

Usage Guidelines4/5

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

Gives the invocation contract explicitly: exactly one of id or path for the source and exactly one of targetParentId or targetParentPath for the destination. It does not, however, state when to prefer copy over move-item or create-item, nor name an alternative, so the routing guidance is incomplete.

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