Skip to main content
Glama

create_sequence

Create a new editing timeline in Adobe Premiere Pro with custom name, resolution, frame rate, and audio settings for video projects.

Instructions

Creates a new sequence in the project. A sequence is a timeline where you edit clips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name for the new sequence
presetPathNoOptional path to a sequence preset file for custom settings
widthNoSequence width in pixels
heightNoSequence height in pixels
frameRateNoFrame rate (e.g., 24, 25, 30, 60)
sampleRateNoAudio sample rate (e.g., 48000)

Implementation Reference

  • Defines the input schema, description, and name registration for the 'create_sequence' tool in getAvailableTools().
    {
      name: 'create_sequence',
      description: 'Creates a new sequence in the project. A sequence is a timeline where you edit clips.',
      inputSchema: z.object({
        name: z.string().describe('The name for the new sequence'),
        presetPath: z.string().optional().describe('Optional path to a sequence preset file for custom settings'),
        width: z.number().optional().describe('Sequence width in pixels'),
        height: z.number().optional().describe('Sequence height in pixels'),
        frameRate: z.number().optional().describe('Frame rate (e.g., 24, 25, 30, 60)'),
        sampleRate: z.number().optional().describe('Audio sample rate (e.g., 48000)')
      })
    },
  • Dispatches execution of the 'create_sequence' tool in the executeTool switch statement by calling the handler.
    case 'create_sequence':
      return await this.createSequence(args.name, args.presetPath, args.width, args.height, args.frameRate, args.sampleRate);
  • Primary handler function for 'create_sequence' tool. Validates input via schema (earlier), calls bridge.createSequence, and formats success/error response.
    private async createSequence(name: string, presetPath?: string, _width?: number, _height?: number, _frameRate?: number, _sampleRate?: number): Promise<any> {
      try {
        const result = await this.bridge.createSequence(name, presetPath);
        return {
          success: true,
          message: `Sequence "${name}" created successfully`,
          sequenceName: name,
          ...result
        };
      } catch (error) {
        return {
          success: false,
          error: `Failed to create sequence: ${error instanceof Error ? error.message : String(error)}`,
          sequenceName: name
        };
      }
    }
  • Bridge helper that generates and executes ExtendScript to call Premiere Pro API app.project.createNewSequence(name, presetPath), returning sequence info.
    async createSequence(name: string, presetPath?: string): Promise<PremiereProSequence> {
      const script = `
        // Create new sequence
        var sequence = app.project.createNewSequence("${name}", "${presetPath || ''}");
        
        // Return sequence info
        JSON.stringify({
          id: sequence.sequenceID,
          name: sequence.name,
          duration: sequence.end - sequence.zeroPoint,
          frameRate: sequence.framerate,
          videoTracks: [],
          audioTracks: []
        });
      `;
      
      return await this.executeScript(script);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action ('creates'). It doesn't disclose behavioral traits such as permissions needed, whether the sequence is saved automatically, error conditions (e.g., duplicate names), or what happens on success/failure. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose in the first sentence and adds a clarifying definition in the second. It's appropriately sized with no wasted words, though it could be slightly more informative.

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 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks behavioral context (e.g., side effects, error handling), usage guidelines, and output details, making it insufficient for safe and effective use by 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%, so the schema fully documents all 6 parameters. The description adds no parameter-specific information beyond implying a sequence is created, which the schema already covers. 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 ('creates') and resource ('new sequence in the project'), and defines what a sequence is ('a timeline where you edit clips'). It distinguishes from siblings like 'create_project' or 'create_bin' by specifying the sequence resource, though it doesn't explicitly contrast with 'create_multicam_sequence'.

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 'create_multicam_sequence' or 'duplicate_sequence'. The description lacks context about prerequisites (e.g., needing an open project) or exclusions, leaving usage unclear.

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