Skip to main content
Glama

get_export_presets

Retrieve available export presets and their settings from Adobe Premiere Pro for configuring video output.

Instructions

Get available export presets and their settings

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches available export presets from the local HTTP API endpoint 'http://localhost:3001/api/export-presets' and formats a list of presets with their settings for display.
    async getExportPresets() {
      try {
        const response = await fetch('http://localhost:3001/api/export-presets');
        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}`,
              },
            ],
          };
        }
    
        const presetsList = data.presets.map(preset => 
          `• **${preset.preset_name}** (${preset.format})\n  📐 ${preset.resolution.width}x${preset.resolution.height} @ ${preset.frame_rate}fps\n  📊 Video: ${preset.bitrate} | Audio: ${preset.audio_codec} @ ${preset.audio_bitrate}`
        ).join('\n\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎥 **Export Presets**\n\n${presetsList}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get export presets**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • mcp-server.js:128-136 (registration)
    Tool registration entry in the ListToolsRequestSchema handler, defining the tool name, description, and empty input schema.
    {
      name: "get_export_presets",
      description: "Get available export presets and their settings",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Input schema definition for the get_export_presets tool, which requires no parameters.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • Dispatch case in the CallToolRequestSchema switch statement that routes calls to the getExportPresets handler method.
    case 'get_export_presets':
      return await this.getExportPresets();
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states it 'gets' data, implying a read-only operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what 'available' means (e.g., user-specific vs. system-wide). For a tool with zero annotation coverage, this is a significant gap.

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 with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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?

Given the tool has no parameters, no output schema, and no annotations, the description is minimally adequate but lacks depth. It explains what the tool does but doesn't cover behavioral aspects or output details, leaving gaps in understanding how to use it effectively in context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100% (though trivial since there are no parameters). The description doesn't need to add parameter semantics, so a baseline of 4 is appropriate as it doesn't miss anything.

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 verb ('Get') and resource ('available export presets and their settings'), making the purpose understandable. It doesn't explicitly distinguish from siblings like 'export_project' or 'get_render_queue', but the specificity of 'export presets' provides some implicit differentiation.

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 is provided on when to use this tool versus alternatives like 'export_project' or 'get_render_queue'. The description implies it's for retrieving preset configurations, but lacks explicit context about prerequisites, timing, or comparisons to sibling tools.

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