Skip to main content
Glama
Antonytm

mcp-sitecore-server

by Antonytm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

query-graphql-default

Destructive

Execute a syntax-checked GraphQL query against Sitecore's default endpoint and return JSON data for content retrieval and integration tasks.

Instructions

Executes a GraphQL query against the Sitecore 'default' endpoint and returns the data as JSON. The query is syntax-checked before it is sent. Note what the endpoint can see: 'edge' serves published content only (unpublished master changes are invisible to it), while 'master' / preview schemas read the authoring database. Use introspection-graphql-default for the schema SDL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesThe GraphQL query document, e.g. 'query($path: String!) { item(path: $path, language: "en") { id name } }'.
variablesNoThe query's variables as a JSON object string, e.g. '{"path": "/sitecore/content/Home"}'. Parsed and sent as the GraphQL variables object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.5

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true. The description adds the syntax-check-before-send behavior, which is genuinely beyond the annotations. However, it does not explain why a query tool is flagged destructive (arbitrary mutations via GraphQL) nor mention side effects, so it only partially complements the annotations.

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?

Three tight sentences: purpose, pre-flight validation, and endpoint visibility semantics. Front-loaded and no filler.

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?

Covers purpose, validation, endpoint visibility differences, and points to the introspection sibling. Given the destructive annotation implies mutations are possible, a brief note about that risk would complete the picture, but the description is otherwise comprehensive.

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% – both query and variables are well documented with examples in the schema. The description adds nothing about the parameters, so baseline 3 is correct.

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+resource ('Executes a GraphQL query against the Sitecore default endpoint') and distinguishes itself from the closely-named sibling introspection-graphql-default in the final sentence.

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

Usage Guidelines4/5

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

Explicitly notes the endpoint visibility semantics ('edge' serves published content only; 'master'/preview read the authoring database) and routes to introspection-graphql-default for schema SDL. No explicit when-not-to-use, but the context is clear.

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