Valmera — AI Video Editor

Make the automatic first cut

make_first_cut

Idempotent

Make Valmera's automatic first cut of an explicit project's analyzed main video: a finished vertical film (the strongest stretch, tightened, with a hook title, captions and the picture reframed for phones), made by the same chain the Studio runs after a first upload. Use it when the user wants a finished video and has not asked for anything more specific, or as the first draft you then refine with the editing tools. Needs index_status 'done'. Returns a job: call wait_for_job, then download_url(kind='preview') to watch it and export_final(edl_version) for the MP4. One first cut per project; calling it again returns the existing one.

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>"
    },
    "name": "make_first_cut"
  }
}

Input Schema

Name	Required	Description	Default
`project_id`	Yes	Explicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false) it discloses the prerequisite index_status='done', the fact that it starts a job rather than returning a video, and the follow-up chain wait_for_job → download_url(kind='preview') → export_final(edl_version). It also adds a concrete idempotency detail: one first cut per project, and a repeat call returns the existing one. It stops short of saying what happens if no main video is analyzed, which keeps it off a 5.

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?

The output definition is front-loaded and all four sentences carry information: what it makes, when to use it, the prerequisite, the follow-up chain, and idempotency. The long parenthetical in the opening sentence is dense but earns its place by describing the artifact.

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?

There is no output schema, and the description compensates by explaining that a job is returned and spelling out the exact follow-up calls to view and export the result. Combined with the index prerequisite and the one-per-project rule, nothing an agent needs in order to call it correctly is missing.

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?

Only one parameter, with 100% schema coverage, so the baseline is already high. The description still reinforces meaning the schema states: the project must be explicit and its main video already analyzed, which tells the agent that a project without an index cannot be used here.

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?

It names a specific verb and resource ('automatic first cut of an explicit project's analyzed main video') and then defines the deliverable precisely: a vertical film built from the strongest stretch, tightened, with hook title, captions and phone reframing. An agent can distinguish this from make_shorts, make_variant_set and the add_* tools without opening another schema.

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 states the selection condition explicitly ('when the user wants a finished video and has not asked for anything more specific'), names the alternative path ('first draft you then refine with the editing tools'), and gives the prerequisite 'Needs index_status done'. When-to-use, when-not and preconditions are all present.

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

All Valmera — AI Video Editor 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.