Skip to main content
Glama

Outil.io

Set video transition

set_video_transition
Destructive

Transition du plan principal vers le suivant ; null retire la transition. Durée réelle limitée à la moitié des deux plans et soustraite à la durée totale. 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>",
      "transition": "<transition>"
    },
    "name": "set_video_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipIdYes
versionYes
projectIdYes
transitionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations (destructive, non-read-only, closed-world), the description discloses three non-obvious behaviours: the effective duration is clamped to half of the two adjacent clips, the transition time is subtracted from the total duration, and the operation requires the current edit version and returns the new one. It does not describe what happens on a stale version (error type) or whether an existing transition is silently overwritten, 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.

Conciseness5/5

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

Three short clauses, each front-loading a distinct fact: action plus null semantics, duration behaviour, then the version precondition and return value. Nothing is repeated or padded, and the most decision-relevant information comes first.

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 compensates by stating that the new version is returned, and it covers the mutation's timing side effect and concurrency requirement. Combined with annotations that already flag destructiveness and closed-world scope, an agent has enough to invoke it correctly, though the omission of clipId/projectId meaning and error behaviour keeps it short of complete.

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 carry the parameter burden. It does explain the two least obvious ones well: 'transition' accepts null to remove, and 'version' means the current version of the edit, with the schema's 0.1–2 duration range further constrained by the half-of-each-clip clamp. However, 'projectId' and 'clipId' are never mentioned (clipId only implied by 'plan principal'), leaving half the parameters undocumented in prose.

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 action and target: setting the transition from the main clip to the next, with 'null' removing it. The verb+resource pairing is unambiguous and no sibling tool (transform, mask, chroma_key) covers this same resource, so an agent can route correctly without opening the schema.

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

Usage Guidelines4/5

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

It gives clear operational context: use a transition object to place a transition, pass null to remove one, and the project must be at its current version. There are no explicit when-not-to-use rules or named alternatives, but for a narrowly scoped mutation tool the conditions are sufficient to act on.

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.