Skip to main content
Glama

Outil.io

Remove video clip

remove_video_clip
Destructive

Retirer un plan ou une piste du montage, sans supprimer le média original. Adapter les pistes/textes qui dépassent via le même lot atomique. 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>"
    },
    "name": "remove_video_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint=true, openWorldHint=false) it adds substantial behavioral context: the deletion is scoped to the timeline and does not remove the original media, the operation cascades adjustments to affected tracks/texts atomically, it requires the current version of the edit for concurrency control, and it returns the new version. These are the exact side effects and preconditions an agent needs before calling a destructive mutation.

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 tight sentences, front-loaded with the action and its key non-destructive nuance, then the ripple behavior, then the version precondition and return value. No filler and nothing repeated from annotations or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter destructive mutation with no output schema and 0% parameter documentation, the description covers scope of destruction, cascading side effects, concurrency requirement, and return value. Only per-parameter detail (notably projectId/clipId semantics) is thin, which is a minor gap given how self-describing the field names are.

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 explains 'version' as requiring the current edit version (optimistic concurrency) and clarifies that the id may target a clip or a track, but it says nothing about projectId vs clipId semantics or id formats, leaving part of the burden on self-evident names.

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 ('Retirer un plan ou une piste du montage') and immediately scopes it apart from media deletion ('sans supprimer le média original'). It is clear what is removed, though the phrase 'plan ou piste' is broader than the tool name remove_video_clip, leaving slight ambiguity about whether tracks are also valid targets.

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?

It establishes the operating context: use this to remove an item from the edit while keeping the source media, with ripple adjustments to overflowing tracks/texts handled in the same atomic batch. There is no explicit exclusion or named alternative sibling (e.g. for deleting media or for moving a clip), so it stops short of full routing guidance.

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.