Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Set caption style

set_caption_style
Idempotent

Changes the visual styling of existing captions while preserving their wording and timing. Only supplied style fields are updated.

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": "set_caption_style"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.
motion_motifNoActive Blueprint motion motif id this event executes; never 'hold'.
emphasis_wordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / style / properties / anchor_x
      Removed value: -{
-  "maximum": 1,
-  "minimum": 0,
-  "type": "number"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / style / properties / anchor_x
      Added value: +{
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  4. Changed3 schema fields changed
    • addedInput schema / properties / style / properties / leading / maximum
      Added value: +2.2
    • addedInput schema / properties / style / properties / leading / minimum
      Added value: +0.5
    • addedInput schema / properties / style / properties / motion_look
      Added value: +{
+  "description": "Browser-drawn caption look, the default for short-form/podcast/premium: editorial = bold sans + big serif-italic emphasis word, hard pops; clean = calm sentence case rising from a blur; lockup = small caps over one huge hero word; pop = outlined hype punches; box = gliding highlight pill; serif = gold serif-italic emphasis; glow = karaoke; stack = giant condensed hero; mono = typewriter. null = presets.",
+  "enum": [
+    "editorial",
+    "clean",
+    "lockup",
+    "pop",
+    "box",
+    "serif",
+    "glow",
+    "stack",
+    "mono"
+  ],
+  "type": "string"
+}
  5. Changed1 schema field changed
    • changedInput schema / properties / style / properties / preset / enum
      Previous value: -[
-  "clean",
-  "documentary",
-  "broadcast",
-  "retro",
-  "neon",
-  "podcast",
-  "reels",
-  "beast",
-  "karaoke",
-  "elegant",
-  "spotlight",
-  "stacked",
-  "iridescent",
-  "chrome",
-  "editorial",
-  "fashion",
-  "luxe",
-  "impact",
-  "lyric",
-  "classic"
-]New value: +[
+  "composed",
+  "clean",
+  "documentary",
+  "broadcast",
+  "retro",
+  "neon",
+  "podcast",
+  "reels",
+  "beast",
+  "karaoke",
+  "elegant",
+  "spotlight",
+  "stacked",
+  "iridescent",
+  "chrome",
+  "editorial",
+  "fashion",
+  "luxe",
+  "impact",
+  "lyric",
+  "classic"
+]
  6. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish idempotent=true, destructive=false, readOnly=false; the description adds real value by disclosing patch semantics ('only supplied style fields are updated'). It says nothing about what a preset does to other fields, what happens to conflicting style/motion_look settings, or whether re-runs accumulate.

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?

Two short sentences, front-loaded with purpose and follow-up with the mutation rule; every clause carries information. Slightly under-sized for the tool's complexity rather than padded.

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

Completeness2/5

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

For a tool with a deep nested style object, 25+ enum fields, no output schema, and preset-vs-explicit-field interaction, two sentences leave major gaps. An agent cannot tell from the description how presets relate to individually supplied fields or how motion_look differs from preset.

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

Parameters2/5

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

With schema coverage at 50% and ~24 nested style properties that are almost all undescribed enums, the description should compensate and does not. Its only parameter-relevant content is the partial-update rule for the style object; presets, motion_look, emphasis_words, and motion_motif go unmentioned.

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 names a specific verb and resource ('changes the visual styling of existing captions') and scopes it to existing captions rather than creation, which separates it from add_captions and the sibling set_caption_fixes/set_caption_mutes. It stops short of explicitly naming those siblings.

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 'existing captions' implies when to use this over caption-creation tools, and 'preserving their wording and timing' implies when not to use the caption-editing siblings. But neither alternative nor any prerequisite (e.g. captions must already exist) is stated outright.

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