Skip to main content
Glama

Outil.io

Remove video keyframes

remove_video_keyframes
Destructive

Retirer les keyframes aux temps source indiqués ; times=null retire toute l’animation et réactive la transformation statique. 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>",
      "times": "<times>"
    },
    "name": "remove_video_keyframes"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesYes
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?

The annotations already flag this as destructive and not read-only, and the description adds real behavior beyond them: times=null wipes the entire animation and reverts to the static transform, an optimistic-concurrency requirement (the current edit version), and the fact that the call returns a new version. It leaves open what happens on a stale version besides 'exige', but the destructive scope is clearly disclosed.

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 tight clauses, with the destructive null case placed ahead of the version and return contract, so nothing is wasted. The only friction is that the description is in French while the title and parameters are English.

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?

With no output schema, the description correctly states that the new edit version is returned, and it covers the destructive null edge case and the version precondition. What remains unstated (out-of-range or duplicate times, behavior on version conflict) is minor for a four-parameter mutator whose safety profile is already in the annotations.

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?

The schema description coverage is 0%, so the description has to carry parameter meaning. It does that well for times, including the null meaning and the source-time units, and explains version as the required current edit version, but clipId and projectId are left to their names and constraints.

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 and resource: removing keyframes at the given source times, plus a clear special case (times=null removes all animation and restores the static transform). The remove/upsert distinction is implicit but obvious, so an agent can tell it apart from the sibling upsert_video_keyframes without opening either schema; it stops short of naming that sibling 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?

The when-to-use context is implied by the two modes it describes: targeted removal at the given times and a full-animation reset when times=null. There is no explicit statement of when to prefer this over upsert_video_keyframes or other timeline mutators, and no preconditions are spelled out beyond the version requirement.

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.