Skip to main content
Glama

Valmera — agentic AI video editor

by io.valmera
OverviewDiscussionsAdmin

Apply look

apply_look

PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. One call sets a whole premium look: captions, grade, texture, transitions and optional music. PREMIUM SYSTEMS (best for reels/shorts) — 'editorial': ivory sans captions whose key words turn gold serif italic, matte filmic grade (lifted blacks, soft highlights, gentle desaturation), light grain + vignette, soft white dips; 'creator_punch': bold uppercase pop captions with a yellow active word, vibrant punchy grade, zoom-punch scene transitions; 'cinematic_doc': clean sentence-case captions that rise in word by word, warm teal/orange cinematic grade, vignette + fine grain, unhurried dips to black; 'mono_noir': noir: deep contrast with the colour pushed down, stacked captions whose hero word slams in (key words red), heavy grain + vignette, glitch transitions; black and white comes as a device on its moment, never as the whole short; 'clean_minimal': large clean white captions that rise in as spoken, near-neutral polish grade, no texture, hard cuts. A system draws captions with the browser motion engine, REPLACES the earlier look's custom grade and whole-video texture, never puts a fade from black on a vertical short, and returns hero-moment templates to place next with add_motion_graphic. A look places NO sound unless transition_sounds=true (sound effects are optional, never rules): then a spaced few of its transitions take an approved library sound. CLASSIC looks: 'hype' (beast xl captions, vibrant, zoom_punch cuts), 'clean' (clean white size-led captions, ungraded), 'cinematic' (elegant captions, cinematic grade + warmth, dip_black), 'luxury' (luxe captions, warm), 'meme' (impact xl captions, flash cuts, grain); their fades apply to landscape only. Transitions fire only at real scene changes (B-roll/inserts/new shots), never on jump cuts. music= takes only the exact slug of a library track the USER picked (offer tracks with ask_user; never 'auto' or a mood — agents never choose music) and lays it as a ducked CC0 bed (-18 to -22 dB) when the edit has no music yet; otherwise omit music. Preserves existing emphasis_words, else picks them from the transcript. Never touches cuts. Every component can be adjusted afterwards with its own tool.

Input Schema

NameRequiredDescriptionDefault
nameYes
musicNoExact slug of the library track the user picked (ask_user offers them). Omit to leave music unchanged.
project_idYesRequired immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess.
transition_soundsNoOpt in to library sounds on a spaced few of the look's scene transitions — only when the user asked for transition sounds. Omit (default) to place none; false removes the look's earlier ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / music / description
      Previous value: -"'auto' = a CC0 library bed in the look's moods; or a mood (upbeat, chill, cinematic, corporate, dramatic, hiphop, ambient, inspiring); or an exact slug from list_music_library. Omit to leave music unchanged."New value: +"Exact slug of the library track the user picked (ask_user offers them). Omit to leave music unchanged."
  2. Changed1 schema field changed
    • addedInput schema / properties / transition_sounds
      Added value: +{
+  "description": "Opt in to library sounds on a spaced few of the look's scene transitions — only when the user asked for transition sounds. Omit (default) to place none; false removes the look's earlier ones.",
+  "type": "boolean"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / music
      Added value: +{
+  "description": "'auto' = a CC0 library bed in the look's moods; or a mood (upbeat, chill, cinematic, corporate, dramatic, hiphop, ambient, inspiring); or an exact slug from list_music_library. Omit to leave music unchanged.",
+  "type": "string"
+}
    • changedInput schema / properties / name / enum
      Previous value: -[
-  "cinematic",
-  "clean",
-  "hype",
-  "luxury",
-  "meme"
-]New value: +[
+  "cinematic",
+  "cinematic_doc",
+  "clean",
+  "clean_minimal",
+  "creator_punch",
+  "editorial",
+  "hype",
+  "luxury",
+  "meme",
+  "mono_noir"
+]
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations only declaring the non-read-only/non-destructive profile, the description carries the real behavioral burden and delivers: it REPLACES the earlier look's custom grade and whole-video texture, places no sound unless transition_sounds=true, ducks music to -18 to -22 dB, never puts a fade from black on a vertical short, and preserves existing emphasis_words. These are exactly the side-effect details an agent needs before invoking.

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?

It is front-loaded with the PROJECT-SCOPED constraint and the core purpose before the long look catalog, and each block does real work. It is nonetheless a very dense, run-on block of prose whose length is only partly justified, so it is efficient without being tight.

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 composite, mutating 4-param tool with no output schema, the description covers the return shape ('returns the project identity with its result', hero-moment templates), the mutation scope, sound behavior, and music rules. Nothing an agent needs to invoke it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single enum param has ten values and the description characterizes each one concretely ('editorial': ivory sans captions turning gold serif italic, matte filmic grade; 'meme': impact xl captions, flash cuts, grain), which is far beyond the bare enum strings. It also adds music semantics (exact library slug, ducked CC0 bed levels, never 'auto') and transition_sounds semantics (opt-in, false removes earlier ones) on top of the ~75% schema coverage.

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 gives a crisp verb+resource: 'One call sets a whole premium look: captions, grade, texture, transitions and optional music.' That clearly distinguishes it from the many single-component siblings (add_captions, set_color_grade, set_transitions). It stops short of naming the nearest analogs (apply_recipe, apply_format_pack), so there is no explicit sibling routing.

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 when each look is appropriate ('best for reels/shorts' for premium systems, fades only on landscape for classic looks), gives hard when-not rules for music ('offer tracks with ask_user; never auto'), for transition_sounds (opt in only when the user asked), and for transitions (only at real scene changes, never on jump cuts). It also tells the agent where to go next ('place with add_motion_graphic') and that every component can be re-tuned with its own tool.

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

All Valmera — agentic 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