Skip to main content
Glama

FilmLab

by com.thefilmradar
OverviewDiscussionsAdmin

Start Export

lab_start_export

Start an ASYNC export render of a project sequence. Returns a job_id immediately (status 'queued') — does NOT block. Then poll lab_get_export with that job_id until status is done|failed. Needs the sequence_id to render (an integer from the project's sequences). derivatives asks for extra cut-downs of the SAME render (portrait for social) alongside the main file — their URLs come back in the finished job's derivatives. The finished job also carries zielmarkt_checkliste (delivery checklist per target market, set with lab_zielgruppe).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
profileNoDelivery profile (default 'web'). See lab_export_profiles. 'alpha_prores4444' and 'alpha_png_sequence' keep transparency and are refused with an explanation unless a clip in the sequence really carries an alpha channel.
qualityNoQuality preset (default 'standard')
project_idYesProject id (from lab_list_projects)
derivativesNoExtra cut-downs rendered from the FINISHED export, on top of the main file. '9x16' is a deterministic crop of the wide render into portrait — what falls outside the portrait frame is gone, not filled in. Their URLs arrive in the completed job's `derivatives`.
sequence_idYesSequence id to render (positive integer as string, e.g. '27')
ohne_cliptonNoLeave the clips' OWN audio out of the export (e.g. a video model whose sound is always on) — the film then sounds only from the bound stems and the mixdown (music bed, narrator). Default false: the clips' own audio is mixed under the bed as before.
include_stemsNoAlso export audio stems separately (default false)
ki_kennzeichnungNoHow the visible AI disclosure (EU AI Act Art. 50(4)) appears when the sequence contains AI material. Default 'minimal': a small 'KI' mark in the corner for the whole film. 'durchgehend': the larger 'KI-verändert' box. 'leitfaden': an 'AI' mark top right for the whole film, as in the German regulator's (Bundesnetzagentur) transparency guide. 'anfang': the mark for the first 4 s plus a 4 s end card. 'abspann': only the 4 s end card. 'anfang' and 'abspann' require werk_kuenstlerisch=true; there is no option without any disclosure.
derivative_regionNoWhich part of the wide frame the portrait crop keeps. Default 'center' — pick 'left' or 'right' when the subject stands off to one side, otherwise the crop cuts it in half.
werk_kuenstlerischNoConfirm the work is artistic, fictional or satirical — only then may the disclosure be limited to the opening or the end card. Set it only when that is true; the choice is recorded with the export.
kennzeichnung_umfangNoFor a film that mixes people-made material ('eigen', see lab_herkunft) with AI material: 'film' (default) marks the whole film; 'abschnitte' shows the mark only while an AI or undeclared clip is on screen. Only with ki_kennzeichnung minimal, durchgehend or leitfaden. Audio counts too: an AI or undeclared sound track (bed, stems, mixdown) runs under the whole film, so the export then marks the whole film and reports umfang_bestellt. Declare own music or dialogue with lab_add_media(herkunft) or lab_herkunft. A film with no AI clip at all carries no mark either way. The choice and the clip-by-clip origin are recorded in the provenance record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • addedInput schema / properties / ohne_clipton
      Added value: +{
+  "description": "Leave the clips' OWN audio out of the export (e.g. a video model whose sound is always on) — the film then sounds only from the bound stems and the mixdown (music bed, narrator). Default false: the clips' own audio is mixed under the bed as before.",
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / kennzeichnung_umfang / description
      Previous value: -"For a film that mixes people-made material ('eigen', see lab_herkunft) with AI material: 'film' (default) marks the whole film; 'abschnitte' shows the mark only while an AI or undeclared clip is on screen. Only with ki_kennzeichnung minimal, durchgehend or leitfaden. A film with no AI clip at all carries no mark either way. The choice and the clip-by-clip origin are recorded in the provenance record."New value: +"For a film that mixes people-made material ('eigen', see lab_herkunft) with AI material: 'film' (default) marks the whole film; 'abschnitte' shows the mark only while an AI or undeclared clip is on screen. Only with ki_kennzeichnung minimal, durchgehend or leitfaden. Audio counts too: an AI or undeclared sound track (bed, stems, mixdown) runs under the whole film, so the export then marks the whole film and reports umfang_bestellt. Declare own music or dialogue with lab_add_media(herkunft) or lab_herkunft. A film with no AI clip at all carries no mark either way. The choice and the clip-by-clip origin are recorded in the provenance record."
  4. Changed1 schema field changed
    • addedInput schema / properties / kennzeichnung_umfang
      Added value: +{
+  "description": "For a film that mixes people-made material ('eigen', see lab_herkunft) with AI material: 'film' (default) marks the whole film; 'abschnitte' shows the mark only while an AI or undeclared clip is on screen. Only with ki_kennzeichnung minimal, durchgehend or leitfaden. A film with no AI clip at all carries no mark either way. The choice and the clip-by-clip origin are recorded in the provenance record.",
+  "enum": [
+    "film",
+    "abschnitte"
+  ],
+  "type": "string"
+}
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag a non-destructive write, but the description adds substantial behavior beyond them: the render is async and does NOT block, it returns a queued job_id, polling is the completion mechanism, alpha profiles are refused with an explanation unless a clip really has alpha, and derivatives are destructive crops ('what falls outside the portrait frame is gone'). It also discloses which artifacts land in the finished job.

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?

Front-loaded with the most decision-relevant facts (async, non-blocking, follow-up tool) and largely free of filler. It is dense and long for a description, but nearly every clause carries operational weight; the closing note on zielmarkt_checkliste is the softest sentence.

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?

No output schema exists and this is an 11-parameter, enum-heavy production tool, so the description carries real burden. It covers the async lifecycle, the job_id/status return, where derivative URLs appear and the checklist field, which is strong output-side context, though it does not touch several schema-documented parameters.

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 all 11 parameters in detail and the baseline is 3. The description only elaborates on derivatives (extra cut-downs of the SAME render, portrait for social) and sequence_id's origin, leaving the other nine parameters to 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?

States a specific verb and resource ('Start an ASYNC export render of a project sequence') and immediately fixes the operational character (async, non-blocking, returns job_id). It distinguishes itself from the sibling poller by naming lab_get_export as the follow-up, so an agent can tell it apart from lab_list_exports, lab_get_export and the other export tools without opening a 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 and a workflow: call this to queue, then poll lab_get_export until status is done|failed, and it names the required input (sequence_id). It does not, however, state when to prefer it over neighbors like lab_schnitt_export or lab_stems_export, nor any explicit 'do not use this when' condition.

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

All FilmLab toolsInspect
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.

Resources