Skip to main content
Glama

import_media

Add video, audio, or image files to your Premiere Pro project by specifying file paths and organizing them into bins for efficient editing workflows.

Instructions

Imports a media file (video, audio, image) into the current Premiere Pro project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filePathYesThe absolute path to the media file to import
binNameNoThe name of the bin to import the media into. If not provided, it will be imported into the root.

Implementation Reference

  • Registration of the 'import_media' MCP tool in getAvailableTools(), defining name, description, and Zod input schema
    {
      name: 'import_media',
      description: 'Imports a media file (video, audio, image) into the current Premiere Pro project.',
      inputSchema: z.object({
        filePath: z.string().describe('The absolute path to the media file to import'),
        binName: z.string().optional().describe('The name of the bin to import the media into. If not provided, it will be imported into the root.')
      })
    },
  • Input schema (Zod) for the import_media tool
    inputSchema: z.object({
      filePath: z.string().describe('The absolute path to the media file to import'),
      binName: z.string().optional().describe('The name of the bin to import the media into. If not provided, it will be imported into the root.')
    })
  • Primary handler for import_media tool: calls bridge.importMedia and formats response with success/error handling
    private async importMedia(filePath: string, binName?: string): Promise<any> {
      try {
        const result = await this.bridge.importMedia(filePath);
        return {
          success: true,
          message: `Media imported successfully`,
          filePath: filePath,
          binName: binName || 'Root',
          ...result
        };
      } catch (error) {
        return {
          success: false,
          error: `Failed to import media: ${error instanceof Error ? error.message : String(error)}`,
          filePath: filePath
        };
      }
    }
  • Dispatch case in executeTool that routes import_media calls to the handler method
    case 'import_media':
      return await this.importMedia(args.filePath, args.binName);
    case 'import_folder':
  • Core bridge handler: executes ExtendScript via executeScript to import media file into Premiere Pro project and return item details
    async importMedia(filePath: string): Promise<PremiereProProjectItem> {
      const script = `
        // Import media file
        var file = new File("${filePath}");
        var importedItem = app.project.importFiles([file.fsName]);
        
        // Return imported item info
        JSON.stringify({
          id: importedItem.nodeId,
          name: importedItem.name,
          type: importedItem.type,
          mediaPath: importedItem.getMediaPath(),
          duration: importedItem.getOutPoint() - importedItem.getInPoint(),
          frameRate: importedItem.getVideoFrameRate()
        });
      `;
      
      return await this.executeScript(script);
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits like required permissions, file format compatibility, error handling, or what happens if the bin doesn't exist. This is inadequate for a mutation tool with zero annotation coverage.

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?

Single sentence, front-loaded with the core action, zero waste. Every word earns its place by specifying media types and project context efficiently.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on success/failure outcomes, side effects, or integration with sibling tools like 'create_bin' for the bin parameter. Should provide more context given the complexity.

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 100%, so the schema fully documents both parameters. The description adds no additional parameter semantics beyond implying media types, which the schema doesn't specify. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Imports') and resource ('a media file into the current Premiere Pro project'), specifying media types (video, audio, image). It distinguishes from siblings like 'import_folder' by focusing on individual files, though it doesn't explicitly contrast them.

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?

No guidance on when to use this tool versus alternatives like 'import_folder' for bulk imports or 'create_project' for new projects. It mentions the current project context but lacks explicit when/when-not instructions or prerequisite checks.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hetpatel-11/Adobe_Premiere_Pro_MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server