Skip to main content
Glama

import_media

Import media files into an editor's project bin; in standalone mode, the first imported video becomes the timeline source.

Instructions

Import media files into the editor's project (bin "OpenEdit"). In standalone mode, the first video imported becomes the timeline source.

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

Input Schema

NameRequiredDescriptionDefault
pathsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose two useful facts: media lands in the 'OpenEdit' bin, and in standalone mode the first video becomes the timeline source. It omits other important traits for a write-like operation, including path format expectations (absolute vs relative, local vs URL), supported formats, whether files are copied or referenced, and behavior on duplicates or failures.

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?

Two short sentences, front-loaded with the core action, and every clause carries information. The parenthetical bin name is slightly awkward but genuinely useful.

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 single-parameter import operation with no annotations and no output schema, the description covers the destination and one notable side effect, which is more than most. It still leaves the agent guessing about path requirements and post-import results, which are exactly the gaps structured fields do not fill here.

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%, so the lone 'paths' array parameter is undocumented apart from the type. The description only implies these are media file paths; it adds no detail on format, relative vs absolute resolution, or whether multiple files are processed in order, which matters given the 'first video becomes the timeline source' rule.

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 and resource ('Import media files into the editor's project') and pins the destination to a named bin ('OpenEdit'). It is clearly distinct from probe_media or place_clips, but the description never explicitly contrasts itself with those siblings, so an agent must infer the boundary from the verb alone.

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 statement of when to use this tool versus alternatives such as probe_media or place_clips. The standalone-mode sentence describes a side effect rather than a usage condition, leaving the agent to infer that import is the required first step in a workflow.

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