Skip to main content
Glama

Outil.io

Add video focus zoom

add_video_focus_zoom

Zoom fluide sur des points d’intérêt (clic, champ, bouton) puis retour : time en secondes SOURCE, x/y en coordonnées de l’image source (0..1). Remplace les keyframes du plan. 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>",
      "points": "<points>"
    },
    "name": "add_video_focus_zoom"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoomNo
clipIdYes
pointsYes
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 declare readOnlyHint=false and destructiveHint=false, and the description adds real behavioral context beyond them: it overwrites the clip's existing keyframes, requires the current version of the edit, and returns the new version (optimistic concurrency). That pre-condition and return value are the kind of operational detail annotations cannot convey. It does not cover permissions or what happens on a version mismatch, so it is not exhaustive.

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?

Extremely dense: the operation, the coordinate/unit conventions, the overwrite semantics and the versioning contract all fit in three short clauses with no filler. It is front-loaded with the operation itself. The switch between the English tool name and the French description is only a minor readability cost.

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 five-parameter mutation tool with a nested points array, zero schema descriptions and no output schema, the description covers the semantics an agent most needs: units, coordinate space, overwrite behavior and the required version round-trip. The remaining gaps (zoom range, hold default, clipId) are modest but real.

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 coverage is 0%, so the description carries the full burden, and it does explain the hardest parts: time is in SOURCE seconds and x/y are source-image coordinates in 0..1, which is essential to call the points array correctly. However, the zoom factor, hold duration, projectId and clipId parameters get no mention, so the compensation is only partial.

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 operation and resource: a smooth zoom onto points of interest (click, field, button) that later returns, applied to a clip. That is far more informative than the title alone. It does not contrast itself with sibling tools such as add_video_text or add_video_layer, so it stops short of a 5.

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 usage context is implied rather than stated: you learn that this creates zoom keyframes on a clip and that it overwrites existing keyframes, which is enough to infer when to reach for it. There is no explicit statement of when not to use it and no named alternative among the many add_video_* siblings.

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.