Skip to main content
Glama

Inspect Film Editorial Workflow

inspect_film_editorial_workflow
Read-onlyIdempotent

Validates a revision-bound editorial manifest against captured source and timeline IDs, building coverage, notes, VFX, story, change-impact and turnover data locally without host edits or exports.

Instructions

Validate a revision-bound film editorial manifest against captured source and timeline identities. Build complete declared coverage review groups, independent picture/audio preferences, screening-note exceptions, story dependencies, VFX state, change impact and a department turnover manifest. Local inspection only: no host edits, exports, automatic creative decisions or verified host claims.

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": {
      "project_id": "<project_id>",
      "expected_context_revision": "<expected_context_revision>",
      "expected_source_revision": "<expected_source_revision>",
      "expected_timeline_revision": "<expected_timeline_revision>",
      "script_revision": "<script_revision>",
      "profile": "<profile>",
      "scenes": "<scenes>",
      "sources": "<sources>",
      "coverage": "<coverage>",
      "occurrences": "<occurrences>",
      "notes": "<notes>",
      "vfx": "<vfx>",
      "storyCards": "<storyCards>",
      "turnover": "<turnover>",
      "viewing": "<viewing>"
    },
    "name": "inspect_film_editorial_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
vfxYesIndependent creative and delivery states; reconciled deliveries require a receipt.
notesYesVersion-bound screening notes. Stale notes remain unresolved; frames are never guessed onto a new cut.
scenesYesExpected script scenes, including those without coverage.
profileYesCustom review preferences; overlap is a review-only source handle in each source timebase.
sourcesYesDeclared source inventory tied to captured source evidence; technical values require host verification.
viewingYesExplicit output viewing profile; rendered-output checks remain required.
coverageYesMany-to-many source-range to scene graph. Preferences never remove unselected coverage.
previousNoOptional previously saved occurrence snapshot for change impact. Caller supplied, not an authenticated host receipt.
turnoverYesRequested turnover settings; handles use each source timebase. This tool creates a manifest, never an export.
project_idYesCaptured project-context ID.
storyCardsYesReorderable story fragments and explicit dependency graph.
occurrencesYesExplicit source/timeline occurrences, separate from source coverage; retimes block automatic handoff.
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.
script_revisionYesHuman-supplied script revision for scene and line identities.
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.
expected_source_revisionYesExact captured source revision.
expected_context_revisionYesExact captured context revision; stale requests fail.
expected_timeline_revisionYesExact captured timeline revision.

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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely useful negative space ('no host edits, exports, automatic creative decisions or verified host claims'), which prevents the agent from assuming the built manifest is authoritative or that turnover is exported. It does not mention failure behavior (stale revisions rejected) or that output is a report, which the schema and output schema carry instead.

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?

Two sentences, front-loaded with the core action and closed with hard constraints. The middle enumeration is long but each item maps to a distinct manifest domain, so it earns its place; slightly denser than ideal for scanning.

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 19-parameter, deeply nested tool with an output schema, the description correctly avoids restating returns and instead covers scope, non-goals, and the manifest domains. The main residual gap is that it does not say when in a workflow to run this versus sibling inspection tools, but nothing needed to call it correctly is missing.

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?

With 100% schema description coverage across 19 parameters, the schema already explains each field in detail. The description only sketches the conceptual domains it consumes (coverage, picture/audio preferences, screening notes, story dependencies, VFX, turnover), which aids orientation but adds no field-level meaning beyond what the nested schemas state.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and object ('Validate a revision-bound film editorial manifest') plus the reference data it checks against ('captured source and timeline identities'), and the second sentence enumerates the review groups it assembles. It is clearly an inspection/validation tool distinct from the apply_/create_ siblings, though it never names an alternative explicitly.

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?

Usage is implied by 'revision-bound' and 'Local inspection only', which signals a pre-edit or pre-turnover validation step, and the exclusions ('no host edits, exports') rule out misuse. However there is no explicit when-to-use statement or routing advice, e.g. whether this replaces inspect_edit_readiness or precedes create_editorial_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