Skip to main content
Glama
Sign In

FilmLab

by com.thefilmradar
OverviewDiscussionsAdmin

Approve Face Fix

lab_face_fix_freigeben

Face fix, step 2 of 2 — PAID: redraw the faces of the stretches that lab_face_fix found, with Kling, and put them back into the clip. Call with get_cost first: the answer lists every stretch with its seconds and price. Charged per stretch; a stretch whose redraw does not pass the check (identity not better, too much flicker) is refunded on its own and stays as the original. A NEW video row comes back; the original stays. The backend refuses with a named reason (face_fix_analyse_nicht_fertig, face_fix_nichts_zu_tun, face_fix_bereits_freigegeben, face_fix_analyse_veraltet, face_fix_analyse_abgelaufen) before anything is charged. An analysis can be approved once and only within 24 hours (the face crops are deleted after that): for another try, run lab_face_fix again (free). Costs credits when called without get_cost.

Input Schema

NameRequiredDescriptionDefault
job_idYesJob id of the finished lab_face_fix analysis — positive integer as string.
get_costNoPreflight: return the stretches and the price per stretch WITHOUT starting anything and without spending. Do this first and let the human confirm.
project_idYesProject id (from lab_list_projects) — positive integer as string.
nur_eigene_datenNoOnly for a model that sends inputs to China or a US recipient without a documented basis, when the step carries images, clips, voices or faces. Means: this material shows or contains no real person other than the human using this account. Set it ONLY after the human has said exactly that for THIS step; never assume it, never reuse it for the next step. Not needed when the human has declared this material in the FilmLab app: the backend reads that declaration, also for material derived from it; only the app can store one. An LK reference, a licensed likeness or another person's agreement does not replace it. Without it the backend refuses with drittland_dritte_gesperrt before any charge; then use a non-gated model or text only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / nur_eigene_daten / description
      Previous value: -"Only for a model that sends inputs to China or a US recipient without a documented basis, when the step carries images, clips, voices or faces. Means: this material shows or contains no real person other than the human using this account. Set it ONLY after the human has said exactly that for THIS step; never assume it, never reuse it for the next step. An LK reference, a licensed likeness or another person's agreement does not replace it. Without it the backend refuses with drittland_dritte_gesperrt before any charge; then use a non-gated model or text only."New value: +"Only for a model that sends inputs to China or a US recipient without a documented basis, when the step carries images, clips, voices or faces. Means: this material shows or contains no real person other than the human using this account. Set it ONLY after the human has said exactly that for THIS step; never assume it, never reuse it for the next step. Not needed when the human has declared this material in the FilmLab app: the backend reads that declaration, also for material derived from it; only the app can store one. An LK reference, a licensed likeness or another person's agreement does not replace it. Without it the backend refuses with drittland_dritte_gesperrt before any charge; then use a non-gated model or text only."
  2. Changed1 schema field changed
    • addedInput schema / properties / nur_eigene_daten
      Added value: +{
+  "description": "Only for a model that sends inputs to China or a US recipient without a documented basis, when the step carries images, clips, voices or faces. Means: this material shows or contains no real person other than the human using this account. Set it ONLY after the human has said exactly that for THIS step; never assume it, never reuse it for the next step. An LK reference, a licensed likeness or another person's agreement does not replace it. Without it the backend refuses with drittland_dritte_gesperrt before any charge; then use a non-gated model or text only.",
+  "type": "boolean"
+}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: charged per stretch, automatic refund for failed redraw checks, a new video row while the original stays, one approval only within 24 hours, named refusal reasons before charging, and credit consumption when get_cost is omitted.

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-loads the critical facts: step 2 of 2 and PAID. It is dense and mostly earns its length, but the long parenthetical error-code list and some repetition around the 24-hour window keep it from being maximally concise.

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?

With no output schema, the description still explains the preflight return (stretches and price), the final result (a new video row, original preserved), refunds, refusal reasons, and the approval window. It is complete for a complex, paid, gated mutation tool.

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 all four parameters already have detailed descriptions. The description adds useful meaning for get_cost by stating it must be called first and that omitting it costs credits, though it adds little new information for project_id and nur_eigene_daten beyond 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 the exact step (step 2 of 2) and the specific action: redraw the faces of stretches found by lab_face_fix and put them back into the clip. It clearly distinguishes this paid approval/redraw tool from the free lab_face_fix analysis step.

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?

Gives explicit sequencing: call with get_cost first and let the human confirm. It also explains the fallback when an analysis is approved or expired: run lab_face_fix again, and use a non-gated model if the gated-material refusal occurs.

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