Skip to main content
Glama

Outil.io

Split video clip

split_video_clip
Destructive

Scinder un clip vidéo ou audio au temps source donné. Les pistes superposées gardent leur position dans le montage. Les keyframes gardent leurs temps source. 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>",
      "sourceTime": "<sourceTime>",
      "newClipId": "<newClipId>"
    },
    "name": "split_video_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
versionYes
newClipIdYes
projectIdYes
sourceTimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and openWorldHint=false, and the description adds real semantic detail beyond that: overlapping tracks keep their position and keyframes keep their source times. It also discloses the optimistic-concurrency requirement and that a new version is returned. What it does not say is what happens to the original clip (whether it is shortened or replaced), which matters for a destructive operation.

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?

Four short sentences, front-loaded with the action, then consequences, then the version contract. No filler, though the keyframe and track sentences could be merged and the version clause is compressed to the point of terseness.

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 destructive five-parameter mutation with no output schema, the description covers the split semantics and version handling but omits the fate of the original clip and the meaning of newClipId. The return value is only gestured at ('renvoie la nouvelle version') without shape, which is acceptable given no output schema.

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 description coverage is 0% for all five required parameters, so the description carries the full burden. It only clarifies two of them, sourceTime ('temps source') and version ('version actuelle du montage'); clipId, projectId and especially newClipId — a caller-supplied identifier for the resulting clip — receive no explanation anywhere.

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?

'Scinder un clip vidéo ou audio au temps source donné' names a specific verb (split), the resource (video/audio clip) and the anchor point (source time), so the operation is unambiguous. It does not, however, distinguish itself from the sibling trim_video_clip, which an agent could easily confuse with splitting.

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?

The description states a precondition ('Exige la version actuelle du montage') and the postcondition ('renvoie la nouvelle version'), which helps an agent sequence calls. It gives no explicit when-to-use vs. when-not-to-use guidance and never points to trim_video_clip or remove_video_clip as alternatives for other editing intents.

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.