Skip to main content
Glama

Outil.io

Create video image clip

create_video_image_clip

Transformer une image (URL https PNG/JPEG/WebP : capture, photo produit, visuel) en plan vidéo animé : zoomIn/zoomOut (Ken Burns), panLeft/panRight, scroll (défile une capture pleine page), none ; fit contain = image entière sur fond flouté.

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": {
      "url": "<url>"
    },
    "name": "create_video_image_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNocover
urlYes
nameNo
ratioNo9:16
motionNozoomIn
secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds genuine behavioral context: accepted image formats, the https requirement, and the fact that fit=contain places the whole image on a blurred background. It does not say where the resulting clip lands, whether it attaches to a project, or what happens on failure.

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?

One dense sentence front-loads the core transformation, then enumerates motion and fit semantics with semicolons. It is efficient and wastes little, though the run-on punctuation and mixed language make it slightly harder to scan than a short structured list would be.

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?

For a 6-parameter mutation tool with no output schema and minimal annotations, the description covers the input side reasonably but omits ratio, seconds, name, and any indication of the returned artifact. An agent could call it, but would be guessing on duration, aspect ratio, and output location.

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 carries the burden and partially meets it: it explains url formats, all six motion values (including Ken Burns for zoom and full-page scrolling), and the meaning of fit=contain. It says nothing about name, ratio, or seconds (default 4, max 60), leaving three of six parameters explained only by their enum/default in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: turning an image (URL https PNG/JPEG/WebP, capture, product photo, visual) into an animated video shot with defined motion types. This clearly separates it from siblings like create_video_background or add_video_clip, which operate on backgrounds or existing clips rather than generating a clip from a still image.

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?

Usage is implied by the input requirements (an image URL and a motion choice), and 'scroll' is scoped to full-page captures, which is a useful usage hint. However, there is no explicit statement of when to prefer this tool over alternatives such as create_video_background or import_image_url, and no prerequisites or exclusions are given.

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.