Skip to main content
Glama

Outil.io

Add video audio track

add_video_audio_track

Ajouter une piste audio indépendante : voix, musique ou bruitage. at est le début dans le montage ; jusqu’à 12 pistes. Un média vidéo avec son est aussi accepté. 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>",
      "track": "<track>"
    },
    "name": "add_video_audio_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior4/5

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

Annotations only declare the safe-mutation profile (readOnly=false, destructive=false, openWorld=false). The description adds real value on top: a hard limit of 12 audio tracks, an optimistic-concurrency requirement ('Exige la version actuelle du montage'), and the fact that a new version is returned. It stops short of describing what happens on a stale-version conflict or how the 12-track cap is enforced, but exceeds annotation coverage meaningfully.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

It is short and front-loads the purpose, so it reads quickly. However, the parameter note begins mid-sentence with a lowercase field name ('at est le début...'), which reads as a fragment pasted into the summary, and the description is in French while the tool name, title, and annotations are English — an inconsistent register that slightly impedes scanning.

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

Completeness2/5

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

For a three-parameter mutation with an eight-property nested object, 0% schema coverage, and no output schema, much is left unstated: asset sourcing, the interaction between start/end/at, speed and volume bounds, and conflict behavior. The versioning note is helpful but the schema-side gap dominates, so an agent cannot call this confidently from the definition alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and there is a nested track object with eight undocumented properties. The description explains only one field ('at' is the start position in the edit) and that 'version' must be current — leaving projectId, id, assetId, name, start vs at, end, speed, and volume undefined. The start-versus-at distinction is exactly the ambiguity an agent would need resolved, and it is not.

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: adding an independent audio track (voice, music, or sound effect), with a stated cap of 12 tracks. It does not distinguish this from sibling tools that also add media to a project (e.g. add_voiceover, add_video_clip), so the agent must infer the boundary. Still clearly identifiable as the audio-track creation operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage-adjacent statements are that a video medium with sound is also accepted and that up to 12 tracks are allowed — these are capabilities/limits, not when-to-use guidance. Nothing tells the agent when to pick this over add_voiceover or add_video_clip, nor any prerequisite workflow beyond needing the current version.

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.