Skip to main content
Glama

Update Workflow Template

update_workflow_template

Replace an existing custom workflow template's definition. This is a full replacement, not a patch: supply name and steps as you want them to end up, because anything omitted is not carried over. Built-in templates are read-only, and only the template's owner may change it. Legacy workflows run in dependency order; steps ready together share one bounded parallel layer, while no depends_on keeps authored list order. Explicitly routed workflows use next_step and bounded quality-gate transitions and cannot mix those fields with depends_on. Requires authentication and the workflows:write scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoTemplate name after the update.
slugYesSlug of the template to replace, from list_workflows.
tagsNoTags after the update.
stepsNoThe complete step list after the update, in run order.
domainNoGrouping domain after the update.
descriptionNoDescription after the update.
expected_template_fingerprintNoOptional. The definition fingerprint you last saw for this template, returned by update_workflow_template when it last succeeded. Supply it and the write refuses, changing nothing, if the stored template is no longer the one that fingerprint names -- someone else edited or deleted it since you read it. Omit it and the write proceeds as it always has, overwriting whatever is there. This is not the definition_sha reported for a run: that one also reflects global configuration, this one names the stored file alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / steps / items / properties / tools
      Added value: +{
      +  "description": "Optional subset of persona tools. [] disables tools for supplied-evidence drafts; omission inherits.",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "type": "array",
      +  "uniqueItems": true
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / steps / items / properties / depends_on / description
      Previous value: -"Optional ids of steps this one builds on. Legacy DAG workflows execute sequentially in topological dependency order; this does not parallelise execution. Do not combine depends_on with routed fields."New value: +"Optional ids of steps this one builds on. A step starts only once every id it names has finished. Steps ready together share one bounded parallel layer in authored order. A definition with no arrows still runs in list order. Do not combine depends_on with routed fields."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": false,
      -  "properties": {
      -    "text": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "text"
      -  ],
      -  "type": "object"
      -}New value: +null
  4. Changed8 schema fields changed
    • addedInput schema / properties / steps / items / allOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "id",
      +        "step_id"
      +      ]
      +    }
      +  }
      +]
    • changedInput schema / properties / steps / items / properties / depends_on / description
      Previous value: -"Optional ids of steps this one builds on. Builder metadata only: it is recorded and returned, and it does NOT reorder or parallelise execution. Steps always run in list order."New value: +"Optional ids of steps this one builds on. Legacy DAG workflows execute sequentially in topological dependency order; this does not parallelise execution. Do not combine depends_on with routed fields."
    • addedInput schema / properties / steps / items / properties / human_gate
      Added value: +{
      +  "description": "Require approval from the authenticated human review UI. API-key and MCP callers cannot cross this gate.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / steps / items / properties / next_step
      Added value: +{
      +  "description": "Optional next step id for an explicitly routed workflow. Do not combine routed fields with depends_on.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^(?:__end__|[A-Za-z0-9][A-Za-z0-9_.:-]*)$",
      +  "type": "string"
      +}
    • addedInput schema / properties / steps / items / properties / quality_gate
      Added value: +{
      +  "additionalProperties": false,
      +  "allOf": [
      +    {
      +      "if": {
      +        "properties": {
      +          "schema": {
      +            "const": "scope_decision/v1"
      +          }
      +        },
      +        "required": [
      +          "schema"
      +        ]
      +      },
      +      "then": {
      +        "properties": {
      +          "blocking_severities": {
      +            "const": [
      +              "P0",
      +              "P1"
      +            ]
      +          },
      +          "max_iterations": {
      +            "const": 1
      +          }
      +        }
      +      }
      +    }
      +  ],
      +  "properties": {
      +    "blocking_severities": {
      +      "items": {
      +        "enum": [
      +          "P0",
      +          "P1",
      +          "P2",
      +          "P3",
      +          "P4",
      +          "P5"
      +        ],
      +        "type": "string"
      +      },
      +      "maxItems": 6,
      +      "minItems": 1,
      +      "type": "array",
      +      "uniqueItems": true
      +    },
      +    "loop_to": {
      +      "maxLength": 100,
      +      "minLength": 1,
      +      "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
      +      "type": "string"
      +    },
      +    "max_iterations": {
      +      "maximum": 5,
      +      "minimum": 1,
      +      "type": "integer"
      +    },
      +    "pass_to": {
      +      "maxLength": 100,
      +      "minLength": 1,
      +      "pattern": "^(?:__end__|[A-Za-z0-9][A-Za-z0-9_.:-]*)$",
      +      "type": "string"
      +    },
      +    "schema": {
      +      "enum": [
      +        "severity_findings/v1",
      +        "scope_decision/v1"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "schema",
      +    "loop_to",
      +    "pass_to",
      +    "max_iterations"
      +  ],
      +  "type": "object"
      +}
    • addedInput schema / properties / steps / items / properties / requires_distinct_provider_from
      Added value: +{
      +  "description": "Require this step's actual provider to differ from the provider that produced the named earlier step.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / steps / items / properties / step_id
      Added value: +{
      +  "description": "Canonical stable identifier for routed steps. Do not supply both step_id and the legacy id field.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9_.:-]*$",
      +  "type": "string"
      +}
    • changedInput schema / properties / steps / items / properties / type / description
      Previous value: -"Optional kind of node. Defaults to 'agent' -- ask a model a question -- which is the only kind this build can execute. 'transform' and 'connector' are accepted and saved so a workflow authored for a later build round-trips, but a run that reaches one fails that single step with a plain message. Do NOT use them for work that must actually run."New value: +"Optional executable node kind. Defaults to 'agent', which asks a model a question. 'transform' runs a supported deterministic local operation; 'connector' invokes the configured connector runtime and fails that step if the runtime is unavailable."
  5. Changed1 schema field changed
    • addedInput schema / properties / expected_template_fingerprint
      Added value: +{
      +  "description": "Optional. The definition fingerprint you last saw for this template, returned by update_workflow_template when it last succeeded. Supply it and the write refuses, changing nothing, if the stored template is no longer the one that fingerprint names -- someone else edited or deleted it since you read it. Omit it and the write proceeds as it always has, overwriting whatever is there. This is not the definition_sha reported for a run: that one also reflects global configuration, this one names the stored file alone.",
      +  "maxLength": 64,
      +  "minLength": 64,
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • addedInput schema / properties / steps / items / properties / params
      Added value: +{
      +  "description": "Optional configuration for a non-agent step. Must be omitted or empty for an 'agent' step, whose configuration is the named fields above (model, temperature, instruction, ...); params would be silently ignored there, so it is refused.",
      +  "type": "object"
      +}
    • addedInput schema / properties / steps / items / properties / type
      Added value: +{
      +  "description": "Optional kind of node. Defaults to 'agent' -- ask a model a question -- which is the only kind this build can execute. 'transform' and 'connector' are accepted and saved so a workflow authored for a later build round-trips, but a run that reaches one fails that single step with a plain message. Do NOT use them for work that must actually run.",
      +  "enum": [
      +    "agent",
      +    "transform",
      +    "connector"
      +  ],
      +  "type": "string"
      +}
  7. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare the safety profile (not read-only, not idempotent, not destructive); the description adds substantial behavior the agent cannot get elsewhere: full-replacement semantics where omitted fields are dropped, ownership requirement, authentication plus the workflows:write scope, and dependency/routing execution rules. This is exactly the value-add the dimension rewards.

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?

The most consequential fact ('full replacement, not a patch') is front-loaded in the second sentence, and every subsequent sentence carries distinct information rather than filler. It is dense but single-paragraph and slightly long relative to what an agent needs at scan time.

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?

For a 7-parameter mutation tool with a nested steps object and no output schema, the description covers replacement semantics, permissions, and execution ordering well. It omits any mention of the returned fingerprint/return shape and the optional optimistic-concurrency parameter, leaving small gaps.

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 every parameter in depth. The description reinforces routing/ordering semantics (depends_on vs next_step) but largely mirrors what the schema already states, and it never mentions the important expected_template_fingerprint concurrency field, so it does not meaningfully exceed the schema baseline.

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 and resource ('Replace an existing custom workflow template's definition'), and the word 'Replace' plus 'custom/existing' cleanly distinguishes it from create_workflow_template and delete_workflow_template in the sibling list. An agent can identify the operation without opening the 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 for use: it is a full replacement rather than a patch, built-in templates are read-only, and only the owner may change it. It stops short of naming sibling alternatives (create/delete) or explicitly saying when NOT to use this, but the ownership and read-only constraints are strong usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources