Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

common-set-item-template

Set or change the template of a Sitecore item using its ID or path, and optionally map fields to copy values between old and new templates.

Instructions

Sets the item template.

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": {
      "template": "<template>"
    },
    "name": "common-set-item-template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the item to set the template for. Supply this or path.
pathNoThe path of the item to set the template for. Supply this or id.
databaseNoDatabase to resolve an id against (default master).
templateYesThe path representing the template item.
fieldsToCopyNoThe key-value pairs map the old template fields to the new template fields. The key represents the old template field, and the value represents the new template field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.1/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 agent knows this is a non-destructive mutation, but the description adds nothing beyond that structured signal. It doesn't say what actually changes when a template is assigned, whether existing field values are affected, or whether the operation requires the item id/path plus a resolvable template.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no wasted words and no burying of key information. However, it is concise by omission rather than by discipline, so it earns only a middling score for structure.

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?

This is a mutation tool with a nested object parameter (fieldsToCopy), no output schema, and no annotations explaining consequences, yet the description says nothing about effects or edge cases. For an operation whose whole point is swapping an item's template and remapping fields, that is a significant gap.

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?

With 100% schema description coverage across all five parameters — including the id/path alternative and the fieldsToCopy old-to-new field mapping — the schema already carries the parameter burden. The description contributes no additional parameter meaning, so the baseline 3 applies.

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

Purpose2/5

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

"Sets the item template" restates the tool name almost verbatim, giving no more information than the identifier already did. It does not distinguish this from close siblings like common-set-base-template, common-get-item-template, authoring-update-item-template, or authoring-create-item-template, so an agent cannot tell which one to reach for.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The sibling common-set-base-template in particular covers a closely related operation, and the description gives the agent nothing to choose 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