Skip to main content
Glama

Preview Workflow Recipe

preview_workflow_recipe
Read-onlyIdempotent

Validates and expands a declarative workflow recipe into guarded MCP routes without invoking routes or changing Premiere, so you can inspect planned steps before execution.

Instructions

Validate and expand one declarative workflow recipe into guarded MCP routes. It does not invoke any route or change Premiere.

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": {
      "recipe_id": "<recipe_id>"
    },
    "name": "preview_workflow_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
recipe_idYesExact built-in or workspace recipe ID.
recipe_fileNoOptional contained JSON file with closed-schema custom recipes.
idempotency_keyNoOptional client-chosen key (1-128 chars of A-Z a-z 0-9 . _ : -) for this intended edit. Pass a fresh key per edit and reuse it only when retrying that same edit, for example after a client-side timeout. A repeat with the same tool, key and arguments is not run again: while the first call is running it fails with IDEMPOTENCY_IN_PROGRESS (poll get_last_operations); after it finished it returns the original outcome marked replayed. A definite failure with nothing applied (receipt outcome not_applied) may be retried with the same key. Reusing a key with different arguments fails with IDEMPOTENCY_KEY_REUSED. Scoped to this MCP session (the stdio server process, or the HTTP server process when Streamable HTTP is stateless per request) and held in memory only (200 keys, 1 hour); it does not survive a restart or reconnect. Read-only invocations are never deduplicated.
provided_inputsNoNames of inputs already available to the caller; values are intentionally not persisted in the recipe preview.
expected_cep_targetNoOptional reviewed CEP sequence/clip identity and exact tick ranges. Checked before every generated command; UXP refuses this CEP-only guard.
expected_project_pathNoOptional absolute saved-project path. Every generated CEP command refuses before its body when the active project differs or is unsaved. UXP commands refuse this CEP-only guard; local-only tools do not inspect Premiere. Omit to keep existing behavior.
approved_workspace_pathNoAbsolute approved workspace containing recipe_file; required with recipe_file.

Output Schema

NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.
receiptNoVersioned common mutation receipt; success never implies rendered verification.
idempotencyNoPresent when idempotency_key deduplicated this call: replayed is true when the original outcome was returned instead of running again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.30.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the read-only and non-destructive annotations, it clarifies that generated routes are not invoked and that Premiere is not changed, which is a useful dry-run guarantee. It does not further describe validation failures or guard behavior, although the detailed schema documents many guard-related inputs.

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?

Two front-loaded sentences communicate the operation, output, and non-execution boundary without repetition or filler. The wording is compact while remaining technically specific.

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?

Together with the annotations, fully documented input schema, and output schema, the description provides enough information for correct basic selection and invocation. Its main remaining gap is workflow-level guidance about prerequisites, when to preview, and what tool to use next.

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%, and all seven parameters are extensively documented there, so the baseline score applies. The description adds little parameter-specific guidance, such as how to choose between recipe_id and recipe_file or when to supply the optional guards.

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 gives specific verbs, resource, cardinality, and result: it validates and expands one declarative workflow recipe into guarded MCP routes. It also distinguishes previewing from execution by explicitly stating that no route is invoked.

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 wording implies use as a dry-run validation and expansion step, while the non-invocation statement provides a basic boundary against using it to execute work. It does not explicitly explain when a preview is recommended or name alternatives for finding recipes or executing the resulting plan.

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