Skip to main content
Glama
gherisalim

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

indexing-find-item

Read-only

Search a named Sitecore Content Search index via SPE when other search surfaces cannot target it, returning paged Items with Skip, First, Returned, and HasMore.

Instructions

Finds items through the Sitecore Content Search API over SPE. Prefer authoring-search where it is available: it needs no SPE, scopes to a subtree with a '_path' criterion, and pages with a real total. For published content, a search query through query-graphql- is also cheaper than this. Reach for this tool when neither is configured, or when you need an index this server's other surfaces cannot address by name. Dates are ISO 8601 (e.g. '2023-10-01T00:00:00Z'). Returns Skip, First, Returned, HasMore and Items; HasMore is how you know to page, since Content Search reports no total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skipNoThe number of results to skip. Defaults to 0.
firstNoThe maximum number of results to return. Defaults to 200, and cannot exceed 500 — page with 'skip' instead.
indexNoThe name of the Sitecore index to search in. e.g., 'sitecore_master_index', 'sitecore_web_index'.sitecore_master_index
criteriaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.3

TDQS

A4.3/5.0
Behavior4/5

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

The readOnlyHint annotation covers safety, and the description adds genuinely new behavioral context: the return shape (Skip, First, Returned, HasMore, Items) and the critical fact that Content Search reports no total, so HasMore governs paging. It does not cover permissions/auth requirements or failure behavior on a missing index, which keeps it short of a 5.

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

Conciseness4/5

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

Front-loaded with the core action, then routing guidance, then paging/format notes; every sentence carries information. The sentences are somewhat long and run-on, but nothing is redundant.

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?

With no output schema, the description correctly fills that gap by naming the returned fields and the HasMore paging signal, and it resolves routing against the crowded sibling set. It stops short of explaining index availability, auth, or error cases, but is complete enough to call 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 75% and the schema itself is unusually rich (field naming conventions, numeric suffixes, filter enum, range syntax). The description adds only the ISO 8601 date format note, which the schema's 'value' description already states. 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.

Purpose5/5

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

States a specific verb (Finds) plus resource and mechanism (items via the Sitecore Content Search API over SPE), and explicitly distinguishes itself from candidates an agent might otherwise pick. An agent can tell it apart from authoring-search, item-service-search-items, and query-graphql without opening the 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?

Explicitly names two preferred alternatives (authoring-search, query-graphql-<schema>), gives reasons for each (no SPE, '_path' subtree scoping, real totals, cheaper for published content), and states the exact condition for reaching for this tool. Nothing is left to inference.

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