Skip to main content
Glama

clip

Extract a video segment between specified start and end times, optionally as GIF, from a file or the currently playing media. Requires ffmpeg in PATH.

Instructions

Extract a video clip segment, optionally as GIF. Requires ffmpeg in PATH.

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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd time in seconds
gifNoExport as GIF instead of MP4
fileNoInput file path (uses currently playing file if omitted)
startYesStart time in seconds
outputNoOutput file path (auto-generated if omitted)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only discloses the ffmpeg environment dependency. It says nothing about whether the output file is overwritten or auto-named, whether the operation blocks for long clips, whether re-encoding degrades quality, or what is returned — all material for a tool that writes files to disk.

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?

Two short sentences, zero filler, with the core action front-loaded and the environment constraint following it. Both sentences carry information an agent can act on.

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?

All parameters are well specified by the schema, but with no annotations and no output schema, the description should say more about the result (the produced file path) and side effects. It is minimally adequate rather than complete for a file-writing media tool.

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%, so all five parameters (start, end, file, output, gif) are already documented, including the fallback to the currently playing file and auto-generated output paths. The description's 'optionally as GIF' merely restates the gif flag, adding no new semantics; baseline 3 applies.

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 specific verb and resource ('Extract a video clip segment') plus a notable variant ('optionally as GIF'), so the agent knows exactly what operation is performed. It does not name or differentiate itself from any sibling, but no sibling in the visible list performs clip extraction, so confusion risk is low.

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

Usage Guidelines2/5

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

'Requires ffmpeg in PATH' is a prerequisite, not usage guidance. There is no statement of when to use this versus related tools (e.g. cast, detect_scenes) or when extraction is inappropriate, leaving the agent to infer the trigger conditions entirely.

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