Skip to main content
Glama

Outil.io

Import video media URL

import_video_media_url
Destructive

Importer une vidéo, un son ou une image depuis une URL publique (normalisé en MP4/MP3 ; une image devient un plan animé). Musique : fournir une URL libre de droits.

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": "import_video_media_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
nameNo
imageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the mutation and open-world nature are covered. The description adds genuine behavioral context beyond that: server-side normalization to MP4/MP3, animated-shot conversion for stills, and the royalty-free constraint for music. It still omits whether the import is synchronous, how long it takes, or what gets destroyed.

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?

Two compact sentences, front-loaded with the action and media types, then the normalization behavior, then the music caveat. Nothing is redundant and the ordering puts the most decision-relevant information first.

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 tool with a nested object, enums, zero schema descriptions, no output schema, and destructive/open-world annotations, the description is too thin on the parameter side. An agent cannot learn from it how to configure the image animation parameters, which is where most of the configuration surface lives.

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 the description says nothing about the three parameters. Most importantly, the nested `image` object (fit, ratio, motion, seconds) — the most complex part of the schema, with enums and a 0.5–60 second bound — is only obliquely referenced by 'une image devient un plan animé', with no explanation of what those knobs do.

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 gives a specific verb+resource (import a video/sound/image from a public URL) and states the transformation outcome (normalized to MP4/MP3, images become animated shots), which is far more useful than the title alone. It does not differentiate from the sibling import_image_url, so the agent must infer that split.

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?

It adds a real usage condition — music must come from a royalty-free URL — and implies the URL must be public, which is actionable context. However, there is no explicit guidance on when to pick this versus import_image_url, or what to do with non-public/uploaded files.

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.