Treza

Update pipeline

update_pipeline

DestructiveIdempotent

Update a pipeline: rename it, change its description, or replace its node graph. For a graph change, read the current one with get_pipeline includeGraph and send the whole graph back, nodes and edges together, every edge naming the two nodes it joins and a port on each, e.g. {"source":"music","sourceHandle":"audio","target":"sequence","targetHandle":"shots"}. A graph with error-level issues is refused with every issue listed, and nothing is saved; settings you change are checked against get_node_type and the live model catalog the same way create_pipeline checks them. To add music, narration or captions to a video a run already made, pass its url from get_run outputs to assemble_video or edit_asset instead: a changed pipeline renders every node again when it runs, the video included, and charges for it.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`edges`	No	The complete new wire list, e.g. {"source":"music","sourceHandle":"audio","target":"sequence","targetHandle":"shots"}. Pass together with nodes; [] for none.
`nodes`	No	The complete new node list. Pass together with edges; the graph is replaced whole.
`pipelineId`	Yes
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

changedInput schema / properties / edges / items / properties / sourceHandle / description

Previous value: -"Output port on the source node: an `outputs` id from get_node_type, e.g. \"audio\" on music-gen or \"video\" on sequence. \"out\" is the generic output the canvas draws."New value: +"Output port on the source node: an `outputs` id from get_node_type, e.g. \"audio\" on music-gen or \"video\" on sequence. \"out\" is the generic output the canvas draws; name the port instead on a node with more than one output besides \"result\" (update_pipeline refuses a new generic wire there)."

changedInput schema / properties / edges / items / properties / targetHandle / description

Previous value: -"Input port on the target node: an `inputs` id from get_node_type, e.g. \"shots\" on sequence or \"prompt\" on music-gen. \"in\" is the generic input the canvas draws, which picks a port by media type at run time; name the port whenever the target has more than one input."New value: +"Input port on the target node: an `inputs` id from get_node_type, e.g. \"shots\" on sequence or \"prompt\" on music-gen. \"in\" is the generic input the canvas draws, which guesses a port by media type at run time; name the port instead on a node with more than one input (update_pipeline refuses a new generic wire there)."

Changed11 schema fields changedSep 24, 2026

addedInput schema / properties / edges / description

Added value: +"The complete new wire list, e.g. {\"source\":\"music\",\"sourceHandle\":\"audio\",\"target\":\"sequence\",\"targetHandle\":\"shots\"}. Pass together with nodes; [] for none."

changedInput schema / properties / edges / items / additionalProperties
```
Previous value: -{}New value: +false
```

addedInput schema / properties / edges / items / description

Added value: +"A wire from one node's output port to another node's input port. An edge is {\"source\": node id, \"sourceHandle\": output port id, \"target\": node id, \"targetHandle\": input port id, \"id\": optional unique id}, e.g. {\"source\":\"music\",\"sourceHandle\":\"audio\",\"target\":\"sequence\",\"targetHandle\":\"shots\"}. Port ids are the ones get_node_type lists under outputs and inputs."

addedInput schema / properties / edges / items / properties

Added value: +{
+  "id": {
+    "description": "Unique id for this wire. Assigned when omitted.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "source": {
+    "description": "Id of the node the wire leaves, as given in `nodes`.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "sourceHandle": {
+    "description": "Output port on the source node: an `outputs` id from get_node_type, e.g. \"audio\" on music-gen or \"video\" on sequence. \"out\" is the generic output the canvas draws.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "target": {
+    "description": "Id of the node the wire enters, as given in `nodes`.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "targetHandle": {
+    "description": "Input port on the target node: an `inputs` id from get_node_type, e.g. \"shots\" on sequence or \"prompt\" on music-gen. \"in\" is the generic input the canvas draws, which picks a port by media type at run time; name the port whenever the target has more than one input.",
+    "minLength": 1,
+    "type": "string"
+  }
+}

removedInput schema / properties / edges / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```

addedInput schema / properties / edges / items / required

Added value: +[
+  "source",
+  "sourceHandle",
+  "target",
+  "targetHandle"
+]

addedInput schema / properties / nodes / description

Added value: +"The complete new node list. Pass together with edges; the graph is replaced whole."

addedInput schema / properties / nodes / items / description

Added value: +"One node: an id, a type from list_node_types, and its config."

addedInput schema / properties / nodes / items / properties

Added value: +{
+  "config": {
+    "additionalProperties": {},
+    "description": "Settings, as get_node_type's configSchema describes them. A node this call adds starts from its type's defaults, and what you pass overrides them.",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  "id": {
+    "description": "Unique id. Edges, and run_pipeline inputs, refer to the node by it.",
+    "minLength": 1,
+    "type": "string"
+  },
+  "label": {
+    "description": "Name shown on the canvas.",
+    "type": "string"
+  },
+  "position": {
+    "description": "Canvas position. Laid out automatically when omitted.",
+    "properties": {
+      "x": {
+        "type": "number"
+      },
+      "y": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "x",
+      "y"
+    ],
+    "type": "object"
+  },
+  "type": {
+    "description": "A node type from list_node_types, e.g. \"file\", \"music-gen\", \"sequence\", \"output\".",
+    "minLength": 1,
+    "type": "string"
+  }
+}

removedInput schema / properties / nodes / items / propertyNames
```
Removed value: -{
-  "type": "string"
-}
```
addedInput schema / properties / nodes / items / required
```
Added value: +[
+  "id",
+  "type"
+]
```

First observedSep 21, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (destructive, non-read-only, idempotent), the description discloses that a graph with error-level issues is refused with all issues listed and nothing is saved, that validations match create_pipeline's checks, and that a changed pipeline re-renders every node and charges for it. This is rich behavioral context.

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 dense paragraph but front-loads the core purpose, then walks through graph-change mechanics, error behavior, validation, and the sibling alternative. Every clause adds actionable information; nothing is wasted.

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

Completeness5/5

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

Given the complexity of replacing a node graph and the presence of destructive/idempotent annotations, the description is complete: it explains the required workflow (read current graph, send whole graph), how edges are structured, what happens on errors, validation compatibility, and cost implications. No output schema is needed for this level of completeness.

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?

With schema description coverage at 40%, the description compensates by explaining the graph-replacement contract: nodes and edges passed together, every edge naming source/target and a port, with a concrete example. It does not elaborate on pipelineId, name, or description, but those are self-evident or covered by the 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 opens with a specific verb and resource — 'Update a pipeline: rename it, change its description, or replace its node graph' — and then details exactly what a graph replacement entails. It also distinguishes itself from siblings like get_pipeline, create_pipeline, assemble_video, and edit_asset by naming them explicitly.

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?

It states when to use this tool versus alternatives: 'For a graph change, read the current one with get_pipeline includeGraph and send the whole graph back' and 'To add music, narration or captions to a video a run already made, pass its url from get_run outputs to assemble_video or edit_asset instead.' This gives direct when/when-not guidance.

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

All Treza tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Update pipeline

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources