Montik

Import media

import_media

Add a video, audio or image file to the media library from a public https URL, such as a generated voiceover or music. Counts against the plan's uploads like any file. For a file on your own machine, use create_upload. Its status says when it is ready; the previews usually take seconds. Optionally place it on the timeline right away. to: folder puts it in the folder's media instead, for every project in the folder (use_asset adds it here).

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_media"
  }
}

Input Schema

Name	Required	Description
`to`	No	folder: the folder's media, shared by its projects (default: this project)
`url`	Yes
`name`	No	file name to show in the library, with its extension (default: from the URL)
`binId`	No	bin to import into (default: library root)
`projectId`	No	Project to act on (default: the open one)
`addToTimeline`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

addedInput schema / properties / to

Added value: +{
+  "description": "folder: the folder's media, shared by its projects (default: this project)",
+  "enum": [
+    "project",
+    "folder"
+  ],
+  "type": "string"
+}

First observedNov 8, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Adds real context beyond the annotations: imports consume the plan's upload quota, processing is asynchronous with status/preview timing, and the timeline placement is optional. It stops short of stating failure modes (non-https URLs, unsupported formats, quota exhaustion errors).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Front-loaded correctly with the action and source constraint, and the quota/timing sentences earn their place. The closing line ('to: folder puts it in the folder's media instead... use_asset adds it here') is awkward, partly redundant with the schema enum description, and its referent for 'here' is unclear.

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?

Covers the import path, quota cost, async readiness, scope choice, and optional timeline placement for a 6-param mutation with no output schema. What's missing is what the agent gets back (asset id/handle) and how to retrieve it after the status turns ready.

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 67% and the description adds meaningful semantics for 'to' (folder means shared media across the folder's projects) and for addToTimeline. It says nothing about binId, name, or projectId, whose meaning is left entirely to the schema (and 'url' has no schema description at all).

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?

States a specific verb and resource ('Add a video, audio or image file to the media library') plus the source constraint ('from a public https URL'), which immediately separates it from local-file siblings.

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

Usage Guidelines5/5

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

Explicitly routes local files to create_upload and explains that use_asset places an existing item rather than importing. It also flags the folder-vs-project scope decision, so the agent knows which path to take before opening the schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Montik tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?