Sitecore AI MCP Server

List Sitecore child items

list_items

Fetches child items of a given Sitecore/XM Cloud parent, with optional template filtering. Returns key details like ID, name, path, and template.

Instructions

List the immediate children of a Sitecore / XM Cloud item. Optionally filter by template id. Returns id, name, path, template name and display name.

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": {
      "parentId": "<parentId>"
    },
    "name": "list_items"
  }
}

Input Schema

Name	Required	Description	Default
`language`	No	Language/locale code, e.g. 'en' or 'en-US'. Defaults to 'en'.	en
`parentId`	Yes	The GUID of the parent item whose immediate children should be listed.
`templateId`	No	Optional template GUID. When provided, only children of this template are returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does add useful details: lists only immediate children, supports an optional template filter, and specifies the returned fields (id, name, path, template name, display name). However, it omits other behavioral aspects such as sorting, pagination, error behavior when parentId is invalid, or language handling. It provides some transparency but not comprehensive.

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?

The description is two concise sentences, front-loaded with the core purpose ('List the immediate children'). Every clause adds value: the scope ('immediate'), the optional filter, and the return fields. No fluff or redundant repetition of the title or tool name.

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?

Given the moderate complexity, full schema coverage, and absence of an output schema, the description is mostly complete. It explains the purpose, the key behavior (immediate children, optional filter), and the return fields. However, it does not mention the language parameter's role or any edge cases, and the sibling tool relationship is not addressed. Still, it provides a solid understanding for an agent to select and use the tool correctly.

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 baseline is 3. The description adds little beyond the schema: it mentions 'immediate children' and optional template filter, both of which are already captured in the parameter descriptions. It does not add new meaning about the language parameter or parameter relationships. The schema fully documents the parameters, so the description does not need to compensate.

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?

The description clearly states the verb 'List' and the resource 'immediate children of a Sitecore / XM Cloud item', which is specific and distinguishes it from the sibling tool get_item_detail that retrieves a single item. It also mentions optional filtering by template ID and the returned fields, making the purpose unmistakable.

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

Usage Guidelines3/5

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

The description implies usage for listing immediate children, but does not explicitly state when to use this tool versus the sibling get_item_detail, nor does it give guidance on when not to use it. The optional template filter is mentioned, but no contextual triggers or exclusions are provided. The usage is clear by implication but not explicitly framed against alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server