Skip to main content
Glama

create_sequence

Create a new video editing sequence in Adobe Premiere Pro with custom name, resolution, and frame rate settings for project organization.

Instructions

Create a new sequence in Premiere Pro

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName of the new sequence
widthNoWidth in pixels (default: 1920)
heightNoHeight in pixels (default: 1080)
framerateNoFrame rate (default: 23.976)

Implementation Reference

  • The handler function that executes the 'create_sequence' tool. It destructures the input arguments, sends a POST request to the local Premiere Pro API endpoint to create the sequence with the specified name, width, height, and framerate, and returns formatted text content with the result or error.
    async createSequence(args) {
      const { name, width = 1920, height = 1080, framerate = 23.976 } = args;
      
      try {
        const response = await fetch('http://localhost:3001/api/create-sequence', {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
          },
          body: JSON.stringify({
            name,
            width,
            height,
            framerate
          }),
        });
        
        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}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `✅ **Sequence Created Successfully**\n\n**Name:** ${data.sequence_name}\n**Resolution:** ${data.resolution.width}x${data.resolution.height}\n**Frame Rate:** ${data.frame_rate} fps\n**Created:** ${data.created_timestamp}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to create sequence**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The input schema for the 'create_sequence' tool, defining the expected parameters: name (required string), optional width, height, framerate (numbers).
    inputSchema: {
      type: 'object',
      properties: {
        name: {
          type: 'string',
          description: 'Name of the new sequence',
        },
        width: {
          type: 'number',
          description: 'Width in pixels (default: 1920)',
        },
        height: {
          type: 'number', 
          description: 'Height in pixels (default: 1080)',
        },
        framerate: {
          type: 'number',
          description: 'Frame rate (default: 23.976)',
        },
      },
      required: ['name'],
    },
  • mcp-server.js:161-186 (registration)
    The tool definition object registered in the ListToolsRequestSchema handler, including the name, description, and input schema for 'create_sequence'.
    {
      name: 'create_sequence',
      description: 'Create a new sequence in Premiere Pro',
      inputSchema: {
        type: 'object',
        properties: {
          name: {
            type: 'string',
            description: 'Name of the new sequence',
          },
          width: {
            type: 'number',
            description: 'Width in pixels (default: 1920)',
          },
          height: {
            type: 'number', 
            description: 'Height in pixels (default: 1080)',
          },
          framerate: {
            type: 'number',
            description: 'Frame rate (default: 23.976)',
          },
        },
        required: ['name'],
      },
    },
  • mcp-server.js:258-259 (registration)
    The switch case in the CallToolRequestSchema handler that routes 'create_sequence' calls to the createSequence method.
    case 'create_sequence':
      return await this.createSequence(args);
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a creation tool, implying mutation, but doesn't mention potential side effects, permissions needed, or what happens if a sequence with the same name exists. This leaves significant gaps in understanding the tool's behavior beyond basic functionality.

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, direct sentence that efficiently conveys the core purpose without unnecessary words. It's front-loaded with the essential 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.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete for a mutation tool. It doesn't cover behavioral aspects like error conditions, return values, or integration with sibling tools. For creating a sequence in a complex application like Premiere Pro, more context is needed to use it effectively.

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?

The input schema has 100% description coverage, providing clear details for all four parameters. The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining relationships between parameters or usage examples. This meets the baseline for high schema coverage.

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 ('Create') and resource ('new sequence in Premise Pro'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'list_all_sequences' or 'get_sequence_details', which would require mentioning this is specifically for creation rather than retrieval or listing.

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. For example, it doesn't mention prerequisites like having a project open, or contrast with tools like 'get_sequence_details' for reading sequences. The description only states what it does, not when or why to use it.

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