Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

presentation-set-rendering-parameter

Add or update a rendering parameter on a rendering placed on a Sitecore item by supplying its unique ID and parameter values.

Instructions

Adds and updates the specified rendering parameter from the rendering placed on an item.

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": {
      "renderingUniqueId": "<renderingUniqueId>",
      "parameter": "<parameter>"
    },
    "name": "presentation-set-rendering-parameter"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe ID of the item holding the rendering. Supply this or path.
pathNoThe path of the item holding the rendering. Supply this or id.
databaseNoThe context database. Only sent when addressing by id -- a path carries its own database prefix (e.g. master:/sitecore/content/Home).master
languageNoThe item language varsion.
parameterYesThe rendering parameter to add or update.
finalLayoutNoTarget the final layout (default true), where list-renderings' uniqueIds live. False = shared only.
renderingUniqueIdYesThe unique ID of the rendering holding the rendering parameter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

C2.5/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 it's a non-destructive write. The description adds no behavioral context beyond that – no mention of required permissions, what happens on conflict, or side effects. With annotations providing only a minimal safety profile, the description carries the burden for mutation semantics and falls short.

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 sentence, but it is grammatically convoluted and slightly misleading ('from the rendering' for an add/update operation). It is concise but not well-structured or front-loaded.

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?

For a mutation tool with no output schema, no annotations beyond basic safety, and siblings that could be confused, the description is incomplete. It doesn't explain what happens to existing parameters, whether it merges or replaces, or how it relates to other presentation tools.

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 7 parameters in detail (id/path alternation, database context, finalLayout behavior). The description adds no parameter semantics beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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

Purpose3/5

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

The description states a verb ('Adds and updates') and a resource ('specified rendering parameter from the rendering placed on an item'), which is clearer than a tautology. However, it is grammatically awkward and doesn't clearly distinguish itself from siblings like presentation-set-rendering or presentation-add-rendering. The phrase 'from the rendering' is confusing for an operation that adds/updates.

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?

No guidance on when to use this tool versus presentation-set-rendering, presentation-add-rendering, or presentation-remove-rendering-parameter. No context about prerequisites or exclusions is provided.

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