Skip to main content
Glama
Sign In
SitecoreMCP

SitecoreMCP

by ramseur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

common-invoke-workflow-by-path

Execute workflow actions on Sitecore items using their file paths to manage content approval processes and state transitions.

Instructions

Executes workflow action for a Sitecore item by its path.

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": {
      "path": "<path>",
      "commandName": "<commandName>"
    },
    "name": "common-invoke-workflow-by-path"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesThe path of the item to have the workflow action executed.
commandNameYesThe name of the workflow command.
commentsNoThe comment to be saved in the history table for the action.
languageNoThe language that will be used as source language.
databaseNoThe database containing the item (defaults to the context database).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.5

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states 'Executes workflow action', implying a mutation operation, but doesn't disclose behavioral traits like required permissions, whether it's destructive (e.g., changes item state), potential side effects (e.g., triggers notifications), or error handling. The description is minimal and lacks essential context for safe use.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded with the core action and resource, making it easy to parse. Every part of the sentence earns its place by specifying key details like 'by its path'.

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

Completeness2/5

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

Given the complexity of a workflow execution tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects (e.g., mutation effects, permissions), usage context, or return values. While the schema covers parameters well, the description fails to provide sufficient guidance for safe and effective use in a Sitecore environment.

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%, with all 5 parameters well-documented in the schema. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain parameter interactions or provide examples). Given the high schema coverage, the baseline score of 3 is appropriate, as the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

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

The description clearly states the verb ('Executes') and resource ('workflow action for a Sitecore item'), specifying it's done 'by its path'. It distinguishes from the sibling 'common-invoke-workflow-by-id' by indicating the path-based approach, though it doesn't explicitly mention the sibling. The purpose is specific and actionable.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as the 'common-invoke-workflow-by-id' sibling. It lacks context about prerequisites (e.g., item must exist, workflow state), exclusions, or typical scenarios. Usage is implied only by the tool name and parameters, with no explicit instructions.

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