GenFlick

level film clip audio

native.level_film_clip_audio

DestructiveIdempotent

Level clip volumes in this Film’s edit when the creator asks. Matches clips with spoken transcript lines to the dialogue level; never raises clips without lines. Leaves takes, sound within clips, music and narration untouched. Free. Omit clip_ids for the whole edit. Waits durably for measurements and refuses a changed edit. Do not offer it unasked.

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.level_film_clip_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.6/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, and the description adds exactly the context an agent needs: what is left untouched (takes, sound within clips, music, narration), the asymmetry that volume is only raised for clips with dialogue, that the operation waits durably for measurements, and that it refuses a changed edit. That materially narrows the blast radius implied by destructiveHint=true.

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?

Purpose comes first, followed by behavioral constraints, cost, and parameter scoping in terse front-loaded clauses with no filler. The clipped telegraphic style ('Free.', 'Do not offer it unasked.') is dense rather than wasteful.

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?

With an output schema present, return values need no explanation, and the description covers scope, exclusions, durability, and cost for a destructive mutation. It stops short of explaining the session prerequisites behind read_skills/expected_catalog_version/request_key, which an agent must still infer from the schema.

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 50%, with read_skills and expected_catalog_version already documented in the schema. The description contributes real meaning for clip_ids ('omit for the whole edit'), but adds nothing about work_id, request_key, or arguments.project_id, so it only partially compensates for the coverage gap.

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?

The description names a specific verb and resource ('Level clip volumes in this Film's edit') and immediately narrows the mechanism: clips with spoken transcript lines are matched to the dialogue level, clips without lines are never raised. That level of specificity clearly separates it from sibling audio tools such as native.edit_film_audio, native.clean_film_take_audio, and native.remove_film_clip_sound.

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?

It gives an explicit trigger ('when the creator asks'), an explicit prohibition ('Do not offer it unasked'), a scoping rule ('Omit clip_ids for the whole edit'), and a cost signal ('Free'). The only gap is that it doesn't name the sibling tools it replaces, but the when/when-not guidance is otherwise unambiguous.

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?