Skip to main content
Glama
Sign In
SitecoreMCP

SitecoreMCP

by ramseur
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

common-invoke-workflow-by-id

Execute workflow actions on Sitecore content items by ID to manage content approval processes. Specify workflow commands and comments to control item progression.

Instructions

Executes workflow action for a Sitecore item by its ID.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe ID 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 full burden. It states 'Executes workflow action' which implies a mutation operation, but doesn't disclose behavioral traits such as required permissions, whether it's destructive, rate limits, or what happens upon execution. This leaves significant gaps for an agent to understand the tool's behavior.

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 appropriately sized and front-loaded, with zero waste.

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 tool involves executing workflow actions (likely a mutation), no annotations, no output schema, and incomplete behavioral disclosure, the description is insufficient. It doesn't cover what the tool returns, error conditions, or prerequisites, leaving the agent with inadequate context for safe and effective use.

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 schema already documents all parameters thoroughly. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't explain workflow command types or comment usage). Baseline 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 action ('Executes workflow action') and resource ('for a Sitecore item by its ID'), making the purpose understandable. However, it doesn't distinguish itself from the sibling tool 'common-invoke-workflow-by-path' which appears to perform the same function but uses a path instead of ID, missing explicit differentiation.

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?

No guidance is provided on when to use this tool versus alternatives. The sibling list includes 'common-invoke-workflow-by-path' which likely serves a similar purpose, but the description doesn't mention this alternative or any context-specific usage scenarios.

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