Skip to main content
Glama

media_import

Import video, audio, or image files—or all media in a folder—into a project, copying originals into the workspace and building a 540p proxy while returning a job ID.

Instructions

Import video, audio or image files (or every media file in a folder) into a project. Copies originals into the workspace and builds a 540p proxy. Returns a jobId.

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>",
      "paths": "<paths>"
    },
    "name": "media_import"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for the job before returning
pathsYesAbsolute paths or ~/... ; folders import their media files
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

With zero annotations the description carries the full burden and does disclose the key side effects: originals are copied into the workspace (disk cost) and a 540p proxy is built (processing cost), and the result is asynchronous. It omits permissions, duplicate/overwrite behavior, and supported formats.

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 sentences, front-loaded with the action, then the side effects, then the return value. No filler.

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?

No output schema exists, so calling out the jobId return is essential and present, along with the workspace-copy and proxy side effects. Missing only the follow-up step (which sibling polls the job) and edge-case behavior for bad or duplicate paths.

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%, so the schema already documents `paths` (including folder expansion) and `wait`. The description's "(or every media file in a folder)" restates rather than extends that, and it says nothing about `wait` or jobId polling semantics.

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?

States a specific verb+resource ("Import video, audio or image files ... into a project") and covers the folder case explicitly. It clearly is not an inspection or analysis tool, though it never names a sibling to contrast with.

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

Usage Guidelines2/5

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

There is no explicit when-to-use, when-not-to-use, or alternative naming (e.g. media_inspect for probing files first, job_status for the returned jobId). The async pattern is only weakly implied by "Returns a jobId".

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