Skip to main content
Glama

Outil.io

Trim video clip

trim_video_clip
Destructive

Définir les points d’entrée et de sortie source d’un plan ou d’une piste. Ne décale pas automatiquement les sous-titres. Exige la version actuelle du montage ; renvoie la nouvelle version.

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": {
      "projectId": "<projectId>",
      "version": "<version>",
      "clipId": "<clipId>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "trim_video_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
clipIdYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description discloses two genuinely useful behaviors: subtitles are not shifted automatically, and the call is version-gated and returns the new version, signalling optimistic concurrency. It does not say what happens to out-of-range or inverted start/end or whether existing keyframes are affected, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the core action, then the caveat and the versioning contract. Every sentence carries distinct information with no filler.

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 five-required-parameter destructive mutation with no output schema, the description covers the version contract and one important side effect but omits units for start/end, the start-before-end rule, and any statement of what the returned new version contains.

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 maps onto start/end ('points d'entrée et de sortie') and version ('version actuelle du montage'), but adds no units for the 0-3600 numeric bounds, no ordering constraint (start < end), and no explanation of projectId or clipId.

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: setting the source in and out points of a clip or track, which is clearly distinct from siblings such as move_video_clip, split_video_clip, or set_video_clip_speed. Minor accuracy gap: it says 'plan ou piste' (clip or track) while the schema only exposes clipId, so the track variant is not actually addressable.

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 implied by the verb (trim = adjust in/out points) and one prerequisite is stated ('Exige la version actuelle du montage'), but there is no explicit when-to-use versus alternatives such as split_video_clip or move_video_clip, and no exclusion conditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.