Skip to main content
Glama

Outil.io

Upsert video keyframes

upsert_video_keyframes
Destructive

Ajouter/remplacer des keyframes interpolées de position, échelle et opacité. time est en secondes SOURCE, même après trim/vitesse. Les autres keyframes sont conservées. 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>",
      "keyframes": "<keyframes>"
    },
    "name": "upsert_video_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
versionYes
keyframesYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation and its risk profile are known before reading the description. The description still earns credit for genuinely non-obvious behavior: time is expressed in SOURCE seconds even after trim or speed changes, unrelated keyframes survive the call, and the operation is version-guarded and returns a new version. What it omits is what happens on a stale version (error vs. overwrite) and whether the keyframe array must be ordered or time-unique, which matters for a destructive upsert.

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, each carrying distinct information, with the core action front-loaded and the caveats (source time, preservation, version) following in priority order. Nothing is padding, though the description is written in French while the surrounding tooling is English, which adds a small parsing cost.

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 mutation with no output schema, full annotation coverage of the safety profile, and 0% schema documentation, this is close but incomplete. The agent knows the units, the merge behavior, and the version contract, but not the failure mode on a version mismatch, whether keyframes must be sorted or time-unique, or what the new version return looks like.

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 carries the whole burden for four required parameters and a nested keyframe object. It does real work: 'time est en secondes SOURCE, même après trim/vitesse' pins down the most error-prone field, the version requirement ('Exige la version actuelle du montage') explains what version means, and 'position, échelle et opacité' maps to x/y, scale, and opacity. It still says nothing about clipId or projectId semantics, keyframe ordering, or the 301-item cap, so it only partly compensates.

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 states a specific verb pair and resource: 'Ajouter/remplacer des keyframes interpolées de position, échelle et opacité'. That is far more precise than the title restatement, and the clarification that other keyframes are preserved separates it from a pure replace/remove semantics. It stops short of naming remove_video_keyframes as the sibling to avoid, so it is clear but not fully differentiated.

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 only implied: 'Les autres keyframes sont conservées' tells the agent this is a merge/upsert rather than a wholesale replacement, which hints at when to pick it. There is no explicit when-to-use, no exclusions, and no routing to remove_video_keyframes or add_video_clip for adjacent tasks.

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.