Skip to main content
Glama
Sign In
video-editor-mcp

video-editor-mcp

by chevrolet231X
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

trim_video

Cut a video segment by specifying a start time and either an end time or duration, saving the result to an output path.

Instructions

Cut a clip out of a video between a start time and either an end time or a duration (seconds).

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

Input Schema

NameRequiredDescriptionDefault
durationNoDuration of the clip in seconds (use this or end_time, not both)
end_timeNoEnd time in seconds (use this or duration, not both)
input_pathYesSource video path. Relative paths resolve against MEDIA_DIR (defaults to the server's working directory); absolute paths are used as-is.
start_timeNoStart time in seconds
output_pathYesDestination path for the trimmed clip. Relative paths resolve against MEDIA_DIR (defaults to the server's working directory); absolute paths are used as-is.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It accurately describes the core trimming action but does not mention practical details like whether the source is preserved, what happens if the output exists, or edge cases such as invalid time ranges.

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?

The description is a single, front-loaded sentence that directly states the operation with no unnecessary words. Every part contributes to understanding the tool's purpose.

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?

For a 5-parameter tool with no output schema, the description covers the core purpose but leaves gaps such as return value, error behavior, and output format expectations. It is adequate but not fully comprehensive for an agent relying solely on this description.

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 description coverage is 100% (all five parameters are described in the schema). The description adds the relational meaning between start_time, end_time, and duration, but this is only a minor enhancement over the schema, which already notes mutual exclusivity.

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?

The description uses the specific verb 'Cut' and identifies the resource as 'a video', clearly defining the operation as extracting a clip between a start time and an end or duration. This distinguishes it from spatial editing tools like crop_video and from extract_frame.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool (trimming videos by time range) but does not explicitly name alternatives or state when not to use it. The context is sufficient for an agent to infer the appropriate scenario.

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

Deploy Server

Other Tools