Skip to main content
Glama

Outil.io

Set video clip volume

set_video_clip_volume
Destructive

Régler le volume d’un plan ou d’une piste audio/vidéo. 0 coupe le son, 1 conserve le niveau 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>",
      "volume": "<volume>"
    },
    "name": "set_video_clip_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
volumeYes
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?

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds real context beyond them by requiring the current edit version (optimistic concurrency) and stating that a new version is returned. It does not explain why the operation is destructive or what permissions are needed, leaving a modest gap.

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 short sentences, zero filler, and the core action is front-loaded before the value semantics and the version/return contract. Nothing repeats the tool name or title unnecessarily.

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?

No output schema exists, and the description usefully covers the return ('renvoie la nouvelle version') and the version precondition. However, for a destructive mutation with 0% schema coverage, the identifiers and the mutating side effects (overwriting existing volume) are not described, so it is not fully self-sufficient.

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% with four required parameters, so the description must compensate. It does well on the two non-obvious ones — volume (0 mutes, 1 preserves source level) and version (must be the current edit version) — but leaves clipId and projectId entirely undocumented.

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?

States a specific verb and resource ('Régler le volume d'un plan ou d'une piste audio/vidéo'), which clearly distinguishes it from siblings like set_video_clip_speed or set_video_transform. Minor imprecision: it mentions audio/video tracks, but the schema only accepts a clipId, so scope is slightly broader than what the tool can actually address.

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?

No explicit when-to-use / when-not-to-use guidance and no named alternatives among the many sibling setters. Usage is only implied by the resource named and by the value semantics (0 = mute, 1 = source level), which help an agent pick the right argument but not the right tool.

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.