GenFlick

Assemble Film Edit

assemble_film_edit

Idempotent

Create a new deterministic edit from the ordered saved scenes and audio tracks; no media regeneration or model call.

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": {
      "project_id": "<project_id>",
      "expected_revision": "<expected_revision>",
      "scene_ids": "<scene_ids>",
      "audio_track_ids": "<audio_track_ids>",
      "request_key": "<request_key>"
    },
    "name": "assemble_film_edit"
  }
}

Input Schema

Name	Required	Description
`scene_ids`	Yes
`project_id`	Yes	Opaque authorized product identifier; never proof of access.
`request_key`	Yes	Stable caller request key; reuse unchanged after a lost response.
`audio_track_ids`	Yes
`expected_revision`	Yes	Current saved resource revision or source signature returned by Genflick.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false, and openWorldHint=false, and the description usefully adds that the operation is deterministic and triggers no model call. However, it does not explain what happens on an expected_revision mismatch, whether a new edit overwrites an existing one, or what ordering constraints apply.

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?

A single front-loaded sentence with a semicolon-delimited qualifier; every clause carries information (resource, inputs, determinism, no generation) and nothing is redundant.

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 an output schema present, return values need not be described, and annotations cover safety and idempotency. For a five-parameter assembly call, the description plus schema supplies enough for correct invocation; the revision-conflict detail is a minor omission.

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?

The schema documents each parameter at 60% coverage, but the description adds genuine meaning absent from the schema: the scenes are "ordered saved" and the edit is "deterministic," implying list order drives the output timeline. It adds nothing for expected_revision or request_key, which the schema already covers.

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?

The description uses a clear verb and resource ("Create a new deterministic edit") and names the input source ("ordered saved scenes and audio tracks"). The clause "no media regeneration or model call" separates it from siblings like generate_scene_media, though it does not explicitly name an alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: assemble when scenes and audio already exist and no generation is desired. The exclusion of regeneration hints at when to use a generation sibling instead, but no alternative is named and no prerequisites (e.g., expected_revision freshness) are stated.

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?