Skip to main content
Glama
Antonytm

mcp-sitecore-server

by Antonytm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

presentation-list-renderings

Read-only

List renderings on a Sitecore item to see a page's composition and component placement, including index, placeholder, name, ID, datasource, and unique ID.

Instructions

Lists the renderings placed on an item — the components that make up the page. This is the tool to use to see a page's composition; presentation-get-layout returns the assigned layout definition item instead. Returns one row per rendering: Index (position in the device's rendering list, which is what presentation-add-rendering and presentation-set-rendering address), Placeholder (the full placeholder path), RenderingName, RenderingID, Datasource and UniqueId. Set includeParameters to add each rendering's Parameters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe ID of the item whose renderings to list (e.g. {110D559F-DEA5-42EA-9C1C-8A5DF7E70EF9}). Supply this or path.
pathNoThe path of the item whose renderings to list (e.g. master:/sitecore/content/Home). Supply this or id.
databaseNoThe database containing the item. Defaults to master, and is only used with id — a path carries its own prefix.
languageNoThe item language. Defaults to the context language.
finalLayoutNoWhich layout to read. Defaults to true (the final layout), which is the effective presentation for the page. Set false to read the shared layout only.
placeholderNoOnly list renderings in this placeholder. Supports wildcards, e.g. '*main*'.
includeParametersNoInclude each rendering's raw Parameters string. Off by default: on an SXA or Stride site the URL-encoded parameter blobs are the largest part of the response by far (they more than doubled a 25-rendering page), and they are rarely what the caller is after. Use presentation-get-rendering-parameter to read a single one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.5

TDQS

A4.7/5.0
Behavior4/5

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

readOnlyHint already covers the safety profile, but the description adds real behavioral context: the row-per-rendering return shape, the field list, and a concrete performance warning that includeParameters can more than double the response on an SXA/Stride page. It doesn't cover auth or pagination, but the added context is substantive.

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?

Front-loaded with purpose, then the sibling boundary, then the return contract and the one behavioral knob. Every sentence carries information and none is redundant.

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

Completeness5/5

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

With no output schema, the description steps in by enumerating the returned fields and their meaning, and covers the default/optional behavior of includeParameters. An agent has everything needed to call and interpret the result.

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 baseline is 3; the description nonetheless adds meaning by explaining why includeParameters is off by default (large URL-encoded blobs) and clarifying that Index is the position that add/set-rendering address, which is not in the schema.

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 (lists) and resource (renderings placed on an item) and immediately scopes it as 'the components that make up the page.' It explicitly distinguishes itself from the sibling presentation-get-layout, so an agent can pick correctly without opening either schema.

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?

Names the alternative (presentation-get-layout) and the condition that selects it ('returns the assigned layout definition item instead'), and points to presentation-get-rendering-parameter for reading a single parameter. When-to-use and the sibling boundary are both explicit.

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