GenFlick

clean film take audio

native.clean_film_take_audio

DestructiveIdempotent

Make a new take of a Film clip with its sound cleaned up, keeping the original take and its picture exactly as they are. No credits are spent. Use it only when the creator asks you to fix a sound problem in a clip, never as an offer. Choose what to fix from what the creator described or what you heard: tone removes a steady hum, whine or drone; crackle softens sharp pops such as fire, rain or static; overall smooths rough, noisy sound but lowers and can dull the whole track. Each is 0 (off), 1 (light), 2 (medium) or 3 (strong); use the lowest that solves the problem. Give start_seconds and end_seconds to clean only part of the clip when the rest holds speech or music that should stay untouched. The cleaned take is selected when ready if the source take was selected; set select_when_ready false to only add it. Waits until the new take is saved.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.clean_film_take_audio"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds meaningfully beyond the annotations: no credits are spent, the source take and picture are preserved, the cleaned take is auto-selected only if the source was selected, and the call blocks until the new take is saved. It does not address retry behavior despite idempotentHint=true on an operation that creates a new take each call, nor any permission requirements, so it is strong but not complete.

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?

Front-loads the outcome and the non-destructive guarantee in the first sentence, then moves through cost, usage gate, setting selection, scoping, and selection semantics in a tight sequence. Every clause carries operational information; there is no filler.

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 blocking, non-destructive create operation with an output schema, the description covers cost, timing, selection side effects and scoping, which is what an agent needs to call it correctly. Remaining gaps are failure handling and the boundary against adjacent audio tools in a very large sibling list.

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?

With 50% schema coverage, the description compensates well for the creative parameters: it defines what tone, crackle and overall each remove, explains the 0-3 scale, warns that overall can dull the whole track, and instructs using the lowest value that works. It also explains that start_seconds/end_seconds restrict cleaning to a section where speech or music must stay untouched, and what select_when_ready changes. Plumbing parameters (work_id, project_id, request_key) remain undiscussed but are self-evident.

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?

States a specific verb and resource: making a NEW take of a Film clip with cleaned sound, while the original take and picture are preserved. That non-destructive framing implicitly separates it from sibling mutators such as native.remove_film_clip_sound or native.level_film_clip_audio, but it never names those alternatives, so the disambiguation is left to inference.

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?

Explicit gating: 'Use it only when the creator asks you to fix a sound problem in a clip, never as an offer' tells the agent both when to call and when not to. It also tells the agent how to pick settings from the creator's description or from what it heard. It stops short of naming the sibling tools to use for other audio cases (removal, leveling, quoting), which would make this a 5.

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

All GenFlick tools Inspect

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

Need Help?