Skip to main content
Glama
kuklaph
by kuklaph

Edit Workflow Settings

cascade_edit_workflow_settings

Update workflow settings for a Cascade container (folder/site). Optionally propagate inherit or require workflow settings to children.

Instructions

Update workflow settings for a Cascade container (folder/site). Optionally propagate to children.

Replaces the container's workflow configuration wholesale. Two boolean flags control propagation: applyInheritWorkflowsToChildren copies the "inherit" setting to descendants, applyRequireWorkflowToChildren copies the "required" setting. Call cascade_read_workflow_settings first so you can pass the existing workflowSettings with only your edits.

Args:

  • identifier (object, required): The container to update

    • id (string, optional): Container ID (preferred)

    • path (object, optional): { path, siteId OR siteName }

    • type (string, required): Typically "folder" or "site"

  • workflowSettings (object, required, shape varies — see Cascade docs): Complete replacement workflow configuration

    • workflowDefinitions (array): Which workflows apply in this container

    • inheritWorkflows (boolean): Whether to inherit from parent

    • requireWorkflow (boolean): Whether workflow is mandatory for edits

  • applyInheritWorkflowsToChildren (boolean, optional, default false): Propagate inheritWorkflows to descendants

  • applyRequireWorkflowToChildren (boolean, optional, default false): Propagate requireWorkflow to descendants

Returns: Cascade OperationResult: { success: true } On failure: { success: false, message: "" }

Examples:

  • Use when: "Require workflow on /releases and all its children" -> set requireWorkflow: true + applyRequireWorkflowToChildren: true.

  • Use when: "Swap a workflow definition on a folder" -> pass the new workflowDefinitions array.

  • Don't use when: You want to advance an in-flight workflow — use cascade_perform_workflow_transition.

  • Don't use when: You only need to read — use cascade_read_workflow_settings.

Error Handling:

  • "Asset not found" when the identifier doesn't resolve

  • "Invalid workflow definition" when a referenced workflow ID is wrong

  • "Permission denied" when credentials lack admin rights. Responses are JSON text; structuredContent is authoritative when the response fits. Oversized responses return bounded _cache metadata for cascade_read_response. For cascade_read, read_mode controls preview versus raw Cascade payload shape.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
identifierNoThe folder whose workflow settings to modify.
workflowSettingsNoREQUIRED: Workflow settings payload (inheritWorkflows, requireWorkflow, workflowDefinitions, etc.). Matches Cascade's WorkflowSettingsSend shape.
applyInheritWorkflowsToChildrenNoApply the 'inheritWorkflows' setting to child folders (default: false).
applyRequireWorkflowToChildrenNoApply the 'requireWorkflow' setting to child folders (default: false).
Behavior5/5

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

Discloses that it 'replaces configuration wholesale' and explains propagation flags. Adds error handling details. Annotations (destructiveHint: false) are consistent; no contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with sections and bullet points, but includes an irrelevant block about bounded _cache metadata and cascade_read response, which bloat the description.

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 all 4 params, return type (OperationResult), error handling, and examples. No output schema but description explains return values. Slightly verbose on unrelated content.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, baseline 3. Description adds significant detail: propagation logic, workflowSettings shape, optionality, and usage examples, elevating meaning beyond schema.

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 description uses a specific verb (Update) and resource (workflow settings for a Cascade container). It distinguishes from siblings by explicitly naming cascade_read_workflow_settings and cascade_perform_workflow_transition.

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

Usage Guidelines5/5

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

Provides explicit when-to-use examples (e.g., 'Require workflow on /releases') and when-not-to-use with alternatives ('Don't use when... cascade_perform_workflow_transition'). Advises reading settings first.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kuklaph/cascade-cms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server