Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Export the finished video

export_final
Idempotent

Creates or recovers a full-resolution MP4 export of an explicitly identified, reviewed edit version. Ownership, upload, timeline, quality and branding checks apply. Repeated requests reuse an existing export or running job; a queued result identifies pending work rather than a completed file.

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

Input Schema

NameRequiredDescriptionDefault
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
edl_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / project_id / description
      Added value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. Added

TDQS

A3.6/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the operational meaning of idempotentHint: repeated requests reuse an existing export or running job, and a queued result signals pending work rather than a finished file. It also names the gating checks (ownership, upload, timeline, quality, branding), which tells the agent what can block success. It stops short of saying how failures surface or how long a job takes.

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?

Three tight sentences, front-loaded with the core action, then preconditions, then repeat-call semantics. No wasted clauses, though the check list is compressed to near-cryptic density.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description should say more about what comes back and how to obtain the file. It partially covers this by distinguishing a queued result from a completed file, but never points to wait_for_job, download_url, or upload_start as the follow-on steps, leaving the agent to infer the retrieval path.

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 coverage is 50%: project_id is well documented in the schema, while edl_version is not. The description's 'explicitly identified, reviewed edit version' adds a little meaning about edl_version being a reviewed version rather than an arbitrary integer, but it does not compensate for the undocumented half of the parameters.

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: 'Creates or recovers a full-resolution MP4 export' of an 'explicitly identified, reviewed edit version'. The full-resolution MP4 framing implicitly separates it from render_preview, though no sibling is named outright.

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?

The phrase 'explicitly identified, reviewed edit version' implies a precondition (the edit must be reviewed and pinned to a version), and the reuse sentence tells the agent what happens on repeat calls. However, it never says when to choose this over render_preview, render_variants, or deliver_aspects, which are the closest alternatives in the sibling list.

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 toolsInspect
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