GenFlick

remove film clip sound

native.remove_film_clip_sound

DestructiveIdempotent

Remove a requested sound with SAM Audio from the exact quoted saved Film video take. Supply exactly one preset_id or custom prompt, quote_id and max_credits from the quote. Saves remaining sound and removed sound as owned WAV outputs; preserves the picture and original. Waits durably for saved results. Defaults to comparison only; select_when_ready true is for an explicit request to use the result and applies only while this picture and its prior audio choice remain selected. Separation can affect wanted sounds: inspect/listen before claiming quality. Never promise perfect removal or regenerate a video to chase the same noise.

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.remove_film_clip_sound"
  }
}

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?

Goes well past annotations: it discloses that two WAV outputs are created, that the picture and original are preserved, that the call waits durably, that the default is comparison-only, and it warns that separation can damage wanted sounds and that quality must be inspected before being claimed. These are exactly the behavioral facts an agent needs for a destructive, long-running, credit-consuming operation.

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 verb, resource and source, then stacks preconditions, side effects, defaults, and cautions in a logical order with no filler. It is dense and slightly run-on, but nearly every clause carries operational information.

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 complex nested-schema, credit-spending, destructive tool with an output schema, the description covers entry preconditions, side effects on assets, async behavior, default vs opt-in behavior, and quality caveats. Return values are legitimately left to the output schema.

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?

Adds real meaning beyond the 50%-covered schema, notably the mutual-exclusivity rule ('exactly one preset_id or custom prompt') that the schema's two nullable anyOf fields do not express, plus the provenance rule for quote_id/max_credits and the scoping condition on select_when_ready. Protocol parameters (work_id, request_key, read_skills) are left 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 ('Remove a requested sound with SAM Audio from the exact quoted saved Film video take') and pins the scope to a quoted, saved take, which distinguishes it from quote_film_clip_sound_removal and the broader native.edit_film_audio / native.clean_film_take_audio siblings.

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 concrete preconditions: supply exactly one preset_id or custom prompt plus quote_id and max_credits 'from the quote', which implies the quoted flow must run first, and it explains when select_when_ready applies ('an explicit request to use the result' and only while the picture and prior audio choice remain selected). It never names the quote tool explicitly, so the routing is implied rather than spelled out.

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?