Skip to main content
Glama
Sign In
Sitecore Community MCP

Sitecore Community MCP

by gherisalim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

authoring-publishing-status

Read-only

Poll the status of a queued publish operation to check whether it is done, failed, or running, and confirm content is live before treating it as published.

Instructions

Reads the status of a publish queued by authoring-publish-item. Returns state (INITIALIZING, QUEUED, RUNNING, ABORTREQUESTED, ABORTED, FINISHED, UNKNOWN), isDone, isFailed and how many items have been processed. Poll this until isDone before treating published content as live.

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": {
      "publishingOperationId": "<publishingOperationId>"
    },
    "name": "authoring-publishing-status"
  }
}

Input Schema

NameRequiredDescriptionDefault
publishingOperationIdYesThe operationId returned by authoring-publish-item, e.g. '4e8ed033-cb59-4484-aa86-a6a165711710;xmc'. Pass it whole, semicolon and suffix included.

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?

Annotations only declare readOnlyHint=true; the description adds substantial context beyond that by enumerating the state values, disclosing isDone/isFailed and the processed-item count, and instructing polling until isDone. This meaningfully enriches the behavioral picture for a read operation.

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 compact sentences with zero waste; the purpose is front-loaded, then return values, then the polling instruction in priority order.

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 compensates by naming the key return fields (state, isDone, isFailed, processed count) and the polling completion condition. Combined with readOnlyHint, an agent has everything needed to call and use it 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 coverage is 100% and the schema itself fully documents publishingOperationId, including the format example and the semicolon-suffix caveat. The description adds no further parameter meaning, so the baseline 3 applies.

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 (Reads) plus resource (status of a publish) and ties it to the exact sibling that produces the operation, authoring-publish-item. An agent can distinguish it from the publish/queue tools in the sibling list without opening any schema.

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?

Gives clear context (use after authoring-publish-item queues a publish) and explicit behavioral guidance ('Poll this until isDone before treating published content as live'). It does not mention alternative status mechanisms such as authoring-get-job, but the when-to-use case is unambiguous.

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