Skip to main content
Glama

video_shorts

Destructive

Trim, caption, and convert selected video segments to vertical format, then export them in one call.

Instructions

Trim, caption, make vertical, and export selected segments in one 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": {
      "input_path": "<input_path>",
      "segments": "<segments>"
    },
    "name": "video_shorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
reviewNoAlso write a review card for the result (default). Reply with the returned preview_directive alone on its own line so Hermes Desktop shows it.
segmentsYes
overwriteNoAllow replacing existing media files.
input_pathYes
output_pathNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / review
      Added value: +{
      +  "default": true,
      +  "description": "Also write a review card for the result (default). Reply with the returned preview_directive alone on its own line so Hermes Desktop shows it.",
      +  "type": "boolean"
      +}
  2. Changed8 schema fields changedv2.0.0
    • removedInput schema / properties / input_path / title
      Removed value: -"Input Path"
    • removedInput schema / properties / output_path / title
      Removed value: -"Output Path"
    • changedInput schema / properties / overwrite / description
      Previous value: -"Explicitly allow replacing existing media. Existing non-media files are protected."New value: +"Allow replacing existing media files."
    • removedInput schema / properties / overwrite / title
      Removed value: -"Overwrite"
    • removedInput schema / properties / segments / title
      Removed value: -"Segments"
    • removedInput schema / properties / style / title
      Removed value: -"Style"
    • removedInput schema / title
      Removed value: -"video_shortsArguments"
    • removedOutput schema / title
      Removed value: -"video_shortsDictOutput"
  3. Addedv1.16.5

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the danger profile is partly carried by structured data. The description adds that four distinct transformations happen in a single pass, which is real behavioral information, but it never says what files are produced, whether existing media is replaced, or that a review card / preview directive may be emitted — all of which matter for a destructive multi-step write.

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 parallel verb list and zero filler. Nothing is repeated and the composite nature of the tool is communicated in the fewest possible words.

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 six-parameter, non-idempotent, destructive tool that writes media, one sentence is thin. An output schema exists so return values need not be described, but the opaque `style` parameter and the unspecified structure of `segments` leave an agent unable to call this correctly without opening the schema and guessing.

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?

Schema coverage is only 33% across six parameters, so the description must compensate and does not. 'Selected segments' loosely maps to segments and 'export' to output_path, but `style` — an untyped anyOf of string/object with no description — is completely unexplained, and `review` / `overwrite` are left to their own schema text.

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 concrete composite action set — trim, caption, vertical-ize, and export — applied to selected segments, which clearly separates it from single-purpose siblings like video_trim or video_add_text. It stops short of naming any of those siblings explicitly, but the phrase 'in one call' signals that this is the batched alternative, so an agent can still discriminate it.

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 only implied by 'in one call' — the reader infers this should be chosen when multiple short-form edits are wanted at once. There is no statement of when NOT to use it, no prerequisites (e.g. whether segments must be pre-split), and no pointer to video_trim / video_edit_ops for single-operation cases.

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