Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

authoring-move-item

Move a Sitecore item and its descendants to a new parent through the Authoring API, preserving all incoming links instead of breaking them via delete-and-recreate.

Instructions

Moves a Sitecore item to another parent over the Authoring and Management API, taking its descendants with it. Every link to the item survives the move — prefer this over delete-and-recreate, which breaks them. Supply exactly one of id or path, and exactly one of targetParentId or targetParentPath.

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-move-item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe item's GUID. Supply this or path.
pathNoThe item's full path. Supply this or id.
databaseNoThe database holding the item. Defaults to master.
sortOrderNoThe sort order to give the item under its new parent.
targetParentIdNoThe GUID of the parent to move into. Supply this or targetParentPath.
targetParentPathNoThe path of the parent to move into. Supply this or targetParentId.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely useful behavior beyond that: descendants move along with the item and all links survive. It does not mention permissions or failure behavior, but this is solid added context.

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 tightly written sentences, front-loaded with what the tool does, then the rationale, then the parameter constraint. Every sentence earns its place with no filler.

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?

For a mutating, non-destructive move with no output schema and fully covered params, the description supplies the mutation behavior, the key side effect (descendants/links), and the exclusivity rule. It stops short of noting permissions or error conditions, but an agent has enough to call it correctly.

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 individual parameters are already documented and the baseline is 3. The description adds a cross-parameter constraint the schema cannot express: supply exactly one of id/path and exactly one of targetParentId/targetParentPath, which is real semantic value for correct invocation.

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 (moves) and resource (a Sitecore item to another parent) and adds scope (descendants travel with it). It is clearly distinguishable from siblings like authoring-copy-item, authoring-delete-item and authoring-update-item.

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

Usage Guidelines5/5

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

Explicitly states when to prefer this tool: 'prefer this over delete-and-recreate, which breaks them.' It gives both a recommended condition and a rejected alternative with the reason, so the agent can route correctly without inference.

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