Skip to main content
Glama

Moderation Transition List

moderation_transition_list

List moderation transitions for a Drupal workflow, or all workflows if no workflow ID is given, to see available content state changes.

Instructions

List a workflow's moderation transitions.

Transitions are configuration inside the workflow entity, not entities of their own, so there is no workflow_transition resource for JSON:API to list. They are read from the workflow's workflow-type plugin (WorkflowTypeInterface::getTransitions()), which is where Drupal keeps them.

Every workflow is read when workflow_id is left out. Naming a workflow that does not exist answers an error listing the ones this site has, rather than an empty list that reads as "no transitions".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_limitNo
page_offsetNo
workflow_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it delivers genuinely non-obvious behavior: transitions come from the workflow-type plugin, and an unknown workflow_id yields an error listing valid workflows rather than a misleading empty list. It does not mention permissions or pagination behavior, but the error semantics disclosure is valuable.

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?

Purpose is front-loaded in the first sentence, and the remaining text earns its place by justifying why there is no JSON:API transition resource. It is slightly verbose with Drupal-internals detail (WorkflowTypeInterface::getTransitions()), but nothing is truly 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?

An output schema exists, so return values need not be described. For a three-parameter list tool the description covers scope and error behavior adequately; the only gap is pagination semantics for page_limit/page_offset.

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 0%, so the description must compensate. It richly explains workflow_id (omitted = all workflows, invalid = error listing existing ones) but says nothing about page_limit or page_offset, leaving two of three parameters undocumented anywhere.

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?

The first sentence gives a specific verb and resource ("List a workflow's moderation transitions"), and the following text distinguishes this from the other moderation_transition_* siblings by explaining that transitions are nested workflow config rather than standalone entities. An agent can tell exactly what this returns.

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

Usage Guidelines3/5

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

The description clarifies scoping behavior ("Every workflow is read when workflow_id is left out"), which is implicit usage guidance, but it never names alternatives such as moderation_transition_get for a single transition or workflow_list. No when-not-to-use is stated.

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