Skip to main content
Glama

FilmLab

by com.thefilmradar
OverviewDiscussionsAdmin

Add Media

lab_add_media

Bring your own video, audio or image into a project — not generated, yours. Two ways: media_url (a public http(s) address; the server fetches it, max 100 MB) or file_name + content_type (you get a signed upload_url and the header that are part of its signature: PUT the file's raw bytes there within the hour with EXACTLY those headers — the answer's anleitung has the ready curl line; a missing header is a 403). Either way the answer is the asset_key — use it in lab_timeline_apply as clips[].asset_key (video) or bett.asset_key (audio). Exception: in projects that check images, an uploaded image is not in the project after the PUT — the answer then carries abschluss_noetig and an abschluss_key; after the PUT call lab_add_media again with the same project_id, art, herkunft and abschluss_key only. That call checks the image and returns the asset_key, or says why it was refused. Free. Internal addresses are refused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
artYesWhat the file is
herkunftYesRequired, no default: 'eigen' = shot, recorded or made by people (no AI generation); 'ki' = generated or altered with AI. Decides the EU AI Act Art. 50 disclosure of every export that uses this file. If the file itself carries an AI mark (C2PA or IPTC source type), it stays AI material whatever you declare, and the answer says so.
file_nameNoName of a local file to upload, with extension. Give this OR media_url
media_urlNoPublic http(s) URL of the file. Give this OR file_name
project_idYesProject id (from lab_list_projects) — positive integer as string
content_typeNoMedia type of the upload, e.g. video/mp4, audio/mpeg — required with file_name
abschluss_keyNoOnly after an upload whose answer said `abschluss_noetig`: the `abschluss_key` from that answer, given AFTER the PUT returned 200. Give it instead of media_url and file_name

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 / abschluss_key
      Added value: +{
+  "description": "Only after an upload whose answer said `abschluss_noetig`: the `abschluss_key` from that answer, given AFTER the PUT returned 200. Give it instead of media_url and file_name",
+  "maxLength": 300,
+  "minLength": 1,
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / herkunft
      Added value: +{
+  "description": "Required, no default: 'eigen' = shot, recorded or made by people (no AI generation); 'ki' = generated or altered with AI. Decides the EU AI Act Art. 50 disclosure of every export that uses this file. If the file itself carries an AI mark (C2PA or IPTC source type), it stays AI material whatever you declare, and the answer says so.",
+  "enum": [
+    "eigen",
+    "ki"
+  ],
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "art"
-]New value: +[
+  "project_id",
+  "art",
+  "herkunft"
+]
  4. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false, so the description carries the real behavioral burden and does so richly: 100 MB cap, server-side fetch, signed upload_url with hour-long validity, exact-header requirement, 403 on missing header, refusal of internal addresses, and that the call is free. It also flags the EU AI Act disclosure consequence and the C2PA/IPTC override on herkunft.

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?

Dense and front-loaded, leading with the purpose and the two paths before edge cases. It is long, but nearly every clause carries operational detail an agent needs (headers, 403, abschluss_key). Slightly heavy on em-dash-embedded asides, which costs it the top mark.

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?

For a 7-parameter tool with no output schema, the description fills the gap by describing all relevant return values (asset_key, upload_url, header, anleitung, abschluss_noetig, abschluss_key) and the full two-phase conditional flow. An agent can complete the call chain end-to-end from this text alone.

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 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the 100 MB limit on media_url, that file_name/content_type yields a signed upload URL and header, and the exact semantics of the abschluss_key follow-up call. It stops short of adding format detail for every field, so not a 5.

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 ('bring your own video, audio or image into a project') and explicitly distinguishes itself from generation ('not generated, yours'), which separates it from siblings like lab_generate. An agent knows exactly what this does 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the two mutually exclusive input paths (media_url vs file_name + content_type), gives the selection condition for each, and describes the conditional abschluss_key re-invocation flow plus the alternative for consuming the result (lab_timeline_apply). Nothing about routing is left to inference.

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