Skip to main content
Glama

export_project

Export Adobe Premiere Pro projects or sequences to video files using customizable presets and audio settings.

Instructions

Export the current project or sequence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_pathYesOutput file path
preset_nameNoExport preset name (default: H.264 High Quality)
include_audioNoInclude audio in export (default: true)

Implementation Reference

  • The handler function that implements the export_project tool logic by making a POST request to the local API endpoint to queue or start the export process.
    async exportProject(args) {
      const { output_path, preset_name = "H.264 High Quality", include_audio = true } = args;
      
      try {
        const response = await fetch('http://localhost:3001/api/export-project', {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
          },
          body: JSON.stringify({
            output_path,
            preset_name,
            include_audio
          }),
        });
        
        if (!response.ok) throw new Error(`HTTP ${response.status}: ${response.statusText}`);
        
        const data = await response.json();
        
        if (data.error) {
          return {
            content: [
              {
                type: 'text',
                text: `⚠️  ${data.error}`,
              },
            ],
          };
        }
    
        if (data.status === 'queued') {
          return {
            content: [
              {
                type: 'text',
                text: `🎬 **Export Queued Successfully**\n\n**Output Path:** ${data.output_path}\n**Preset:** ${data.preset_name}\n**Sequence:** ${data.sequence_name}\n**Queue Position:** ${data.queue_position}\n**Estimated Duration:** ${data.estimated_duration}`,
              },
            ],
          };
        } else {
          return {
            content: [
              {
                type: 'text',
                text: `✅ **Export Started Successfully**\n\n**Output Path:** ${data.output_path}\n**Preset:** ${data.preset_name}\n**Sequence:** ${data.sequence_name}\n**Status:** ${data.status}`,
              },
            ],
          };
        }
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to export project**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The tool schema defining the name, description, input parameters, and validation for the export_project tool.
    {
      name: 'export_project',
      description: 'Export the current project or sequence',
      inputSchema: {
        type: 'object',
        properties: {
          output_path: {
            type: 'string',
            description: 'Output file path',
          },
          preset_name: {
            type: 'string',
            description: 'Export preset name (default: H.264 High Quality)',
          },
          include_audio: {
            type: 'boolean',
            description: 'Include audio in export (default: true)',
          },
        },
        required: ['output_path'],
      },
    },
  • mcp-server.js:261-262 (registration)
    The dispatch/registration in the switch statement that routes calls to the export_project handler.
    case 'export_project':
      return await this.exportProject(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action ('Export') but doesn't explain what this entails—e.g., whether it's a destructive operation, requires specific permissions, has side effects like locking files, or what the output format might be. This leaves critical behavioral traits unspecified.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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?

Given the complexity of an export operation (potentially involving file I/O, rendering, and system resources), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, output, error handling, or how it fits into the broader context of sibling tools, leaving significant gaps for an AI agent.

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%, meaning all parameters are documented in the schema itself. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify what 'current project or sequence' means in relation to parameters). With high schema coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract.

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 ('Export') and the target resource ('the current project or sequence'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_export_presets' or 'get_render_queue', which might be related to export workflows but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active project), exclusions, or how it relates to siblings like 'get_export_presets' for preset selection or 'get_render_queue' for managing exports.

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/jordanl61/premiere-pro-mcp-server'

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