Skip to main content
Glama

trim_clip

Trim a video clip to a specified start and end time, removing unwanted footage such as a melting or corrupted tail.

Instructions

Keeps only start..end seconds. Good for cutting the end of a clip where it starts to melt.

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": {
      "video": "<video>"
    },
    "name": "trim_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
startNo
videoYes

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?

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description does not say whether the original video is preserved or overwritten, whether a new clip/file is produced, or how the null 'end' default is resolved — meaningful gaps for a mutating tool.

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 with the core behavior front-loaded and no wasted setup. The second sentence adds a use-case rather than filler, though the colloquial 'starts to melt' is slightly informal for a technical contract.

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 three-parameter mutating tool with no annotations beyond safety hints, no output schema, and zero schema descriptions, the definition is thin. An agent still cannot tell what the tool returns, whether the source clip is modified, or what happens when 'end' is omitted.

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 0%, so the description must carry parameter meaning; it does clarify that start/end are measured in seconds and define the retained range. It leaves the 'video' parameter and the meaning of a null 'end' (presumably trim to clip end) unstated, so compensation is only partial.

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 uses a specific verb and scope ('Keeps only start..end seconds') that pins down trimming to a time range on a clip. It is clearly distinguishable from siblings like extend_clip or loop_clip without opening a schema, though it never names those alternatives explicitly.

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?

It offers one concrete scenario ('cutting the end of a clip where it starts to melt'), which gives some implied when-to-use context. However, there is no guidance on trimming the head (start=0 default), no exclusions, and no mention of the sibling tools an agent might pick instead.

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