Skip to main content
Glama

Save workflow inputs and settings

playground_workflow_inputs_set
DestructiveIdempotent

Save text/List inputs, prompts, formats, durations, audio settings and image reference choices from workflow_inspect. Free, atomic, revision checked and idempotent. Completed, active and approved steps are read-only, including their shared inputs. Does not generate or approve anything. Returns the refreshed workflow form. Upload new reference media first; choose its existing node 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": {
      "projectId": "<projectId>",
      "expectedRevision": "<expectedRevision>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "playground_workflow_inputs_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesNo
inputsNo
projectIdYesID of the Playground project chosen for this task; obtain it from project creation, an explicit project link or current context.
idempotencyKeyYesUnique key for this request; reuse only when retrying the identical request after a lost response. Use a new key after quoting or changing inputs.
expectedRevisionYesCurrent canvas revision from canvas_read; on revision_conflict, read again and rebuild the change.

Output Schema

NameRequiredDescriptionDefault
nextYesSuggested next action; it does not authorize spending.
savedYes
stepsYes
inputsYes
statusYes
replayedYes
revisionYes
workflowYes
canvasUrlYes
executionYes
projectIdYes
readyNodeIdsYes
lockedNodeIdsYes
completedNodeIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true; the description adds substantive context beyond that — the operation is free and atomic, revision-checked, and completed/active/approved steps (including shared inputs) are read-only. It still does not explain what exactly gets overwritten when destructiveHint is true, which is the one gap for a mutating tool.

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?

Six tight sentences, front-loaded with the action and payload, then behavior, then constraints and prerequisites. No filler, though the enumeration of saved field types is dense enough to read as a list rather than prose.

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?

With an output schema present, the description need not detail the return value, and it still notes the refreshed workflow form. For a five-parameter, destructive, revision-guarded mutation it covers safety, atomicity, read-only scope, and prerequisites; only the precise overwrite behavior is unstated.

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 60%, and the description compensates by mapping the conceptual payload (text/List values, prompts, formats, durations, audio settings, reference choices) onto the inputs/nodes arrays, plus the operational rule that reference media must be uploaded first and referenced by existing node ID. Revision and idempotency semantics are left to the schema, which is appropriate.

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 names a specific verb (Save) and a precise resource set (text/List inputs, prompts, formats, durations, audio settings, image references) and ties the data source to workflow_inspect. An agent can distinguish this from siblings like workflow_run or workflow_quote 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?

It gives real context: the inputs come from workflow_inspect, it explicitly does not generate or approve anything, and it states the prerequisite that new reference media must be uploaded first with its existing node ID. It stops short of naming an explicit alternative for the generate/approve cases, but the exclusions are clear enough to route correctly.

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.