Skip to main content
Glama

Outil.io

Set video clip speed

set_video_clip_speed
Destructive

Régler la vitesse de lecture et de rendu entre 0,5 et 2. La durée du clip change ; vérifier les textes et autres pistes. 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>",
      "speed": "<speed>"
    },
    "name": "set_video_clip_speed"
  }
}

Input Schema

NameRequiredDescriptionDefault
speedYes
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, closed-world), the description discloses two behaviors the annotations cannot: duration changes ripple to text and other tracks, and the call needs the current montage version and returns the new version. It does not state what happens to the prior version or whether the change is reversible, which keeps it below 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short semicolon-separated clauses, each carrying distinct information, with the core operation and range front-loaded. The one structural weakness is the language mismatch with the English tool name and title, which slightly raises parsing effort for an otherwise tight definition.

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 4-required-param destructive mutation with no output schema, the description covers the operation, the value range, the ripple effects on other tracks, the version prerequisite, and the return value. What remains uncovered is identifier semantics and any note on undo or failure modes when the version is stale.

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 compensate. It explains the meaning and bounds of 'speed' and clarifies that 'version' is an optimistic-concurrency token ('Exige la version actuelle du montage'), but projectId and clipId are never characterized, leaving half the parameters without semantic support.

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 ('Régler la vitesse de lecture et de rendu') plus the allowed range 0.5–2, which is a concrete operation an agent can identify. It does not distinguish itself from duration-altering siblings such as trim_video_clip or split_video_clip, so the sibling differentiation that would earn a 5 is absent.

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?

It conveys implied usage context (changing speed alters duration, so captions and other tracks must be re-checked) and a prerequisite (the current edit version is required). However, it never says when to choose this tool over a trim or move operation, and it offers no explicit exclusions.

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.