Skip to main content
Glama

Outil.io

Reorder video layers

reorder_video_layers
Destructive

Définir l’ordre complet des superpositions vidéo, du fond vers le premier plan. Tous les ids existants doivent apparaître exactement une fois. 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>",
      "ids": "<ids>"
    },
    "name": "reorder_video_layers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
versionYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real context beyond that: it is a full-order replacement requiring every existing id exactly once, it needs the current version (optimistic concurrency), and it returns the new version. It does not state what happens on a stale version or on a missing/duplicate id, which is the main remaining gap for a destructive mutation.

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 sentences, front-loaded with the core operation, then constraints, then preconditions and return value. No wasted wording. Minor friction only in that the description is in French while the title and sibling surface 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?

For a destructive, version-guarded mutation with no output schema, the definition covers purpose, the full-replacement contract, the concurrency precondition, and the return value ('renvoie la nouvelle version'). Only error behavior on version conflict or invalid id sets is missing, which keeps it out of the top band.

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

Parameters4/5

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

With 0% schema description coverage, the description must carry the parameter meaning, and it does: 'ids' is the complete ordered list from background to foreground with the exactly-once cardinality rule, and 'version' is explicitly the current montage version. 'projectId' is left to the schema, which is acceptable given its uuid format, but the maxItems=6 cap and the id string constraints are unexplained.

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 ('Définir l'ordre complet des superpositions vidéo') plus a precise semantic orientation ('du fond vers le premier plan'), which makes the full-replacement nature of the operation clear. It doesn't name a sibling (e.g., move_video_track or add_video_layer) to contrast with, so differentiation is inferred rather than stated.

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 phrase 'ordre complet' plus the constraint that all existing ids must appear exactly once implicitly signals this is for whole-stack reordering rather than incremental movement, and the version requirement is a precondition. However, there is no explicit when-to-use vs when-not guidance and no named alternative for a partial reorder.

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.