Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

presentation-get-rendering

Read-only

Retrieve a rendering definition from a Sitecore item by ID or path, with optional filters for database, language, placeholder, data source, and final layout.

Instructions

Gets rendering definition on an 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": "presentation-get-rendering"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoThe id of the item to retrieve rendering for. Supply this or path.
pathNoThe path of the item to retrieve rendering for. Supply this or id.
databaseNoDatabase to resolve an id against (default master).
languageNoThe item language filter.
uniqueIdNoThe rendering definition unique id.
dataSourceNoThe rendering data source filter.
finalLayoutNoTarget the final layout (default true), where list-renderings' uniqueIds live. False = shared only.
placeholderNoThe rendering datasource filter.

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 already declare readOnlyHint=true, so the safety profile is covered, but the description adds nothing beyond 'Gets' — no mention of scoping, filtering behavior, or what a 'rendering definition' contains. For a query tool with 8 optional parameters and non-obvious semantics (finalLayout, uniqueId), the description should disclose more.

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 filler and no hedging — front-loaded and efficient. However, it is arguably under-specified rather than truly concise, so it does not earn a top score.

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?

With no output schema and 8 parameters covering a domain-specific concept (rendering definitions, placeholders, data sources, final vs shared layout), the one-line description leaves an agent without enough context to know what it will receive or how this differs from its 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 the parameter documentation already lives in the schema (id/path alternatives, database default, finalLayout semantics). The description adds no additional parameter meaning, which is the expected baseline of 3 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?

States a verb (Gets) and a resource (rendering definition on an item), but 'rendering definition' is ambiguous — it reads almost identically to sibling tools like presentation-list-renderings, presentation-get-layout, and presentation-get-rendering-parameter. An agent cannot reliably tell from this sentence alone which of those to pick.

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?

There is no guidance about when to use this tool versus the many sibling presentation-* read/set/add/remove tools, and no prerequisites or conditions are stated. The agent must infer usage entirely from the name.

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