Skip to main content
Glama

get_sequence_details

Retrieve comprehensive details about a Premiere Pro sequence, including tracks, effects, and markers, to analyze or automate video editing workflows.

Instructions

Get detailed information about a specific sequence including tracks, effects, and markers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequence_nameYesName of the sequence to get details for

Implementation Reference

  • Executes the tool logic by fetching sequence details from localhost:3001/api/sequence-details, processing video/audio tracks, effects, and markers, and returning a formatted text response.
    async getSequenceDetails(sequenceName) {
      try {
        const response = await fetch(`http://localhost:3001/api/sequence-details?name=${encodeURIComponent(sequenceName)}`);
        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 videoTracks = data.tracks.video_tracks.map(track => 
          `  β€’ Track ${track.track_number}: ${track.track_name} (${track.clip_count} clips) ${track.is_locked ? 'πŸ”’' : ''} ${track.is_visible ? 'πŸ‘οΈ' : 'πŸ™ˆ'}`
        ).join('\n');
    
        const audioTracks = data.tracks.audio_tracks.map(track => 
          `  β€’ Track ${track.track_number}: ${track.track_name} (${track.clip_count} clips) ${track.is_locked ? 'πŸ”’' : ''} ${track.is_muted ? 'πŸ”‡' : 'πŸ”Š'} ${track.is_solo ? '🎯' : ''}`
        ).join('\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎬 **Sequence Details: ${data.sequence_name}**\n\n**Settings:**\nβ€’ Resolution: ${data.settings.resolution.width}x${data.settings.resolution.height}\nβ€’ Frame Rate: ${data.settings.frame_rate} fps\nβ€’ Audio: ${data.settings.audio_sample_rate} Hz\n\n**Video Tracks:**\n${videoTracks}\n\n**Audio Tracks:**\n${audioTracks}\n\n**Applied Effects:** ${data.effects_applied.join(', ')}\n**Markers:** ${data.markers.length}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get sequence details**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Defines the tool schema with input requiring 'sequence_name' string.
    {
      name: "get_sequence_details",
      description: "Get detailed information about a specific sequence including tracks, effects, and markers",
      inputSchema: {
        type: "object",
        properties: {
          sequence_name: {
            type: "string",
            description: "Name of the sequence to get details for"
          }
        },
        required: ["sequence_name"]
      }
    },
  • mcp-server.js:231-233 (registration)
    Registers the handler dispatch in the CallToolRequest switch statement.
    case 'get_sequence_details':
      return await this.getSequenceDetails(args.sequence_name);
  • mcp-server.js:31-214 (registration)
    Registers the tool in the ListToolsRequestHandler by including it in the tools array.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => {
      const tools = [
        {
          name: "get_project_info",
          description: "Get basic information about the current Premiere Pro project",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_active_sequence_info", 
          description: "Get detailed information about the currently active sequence",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "list_all_sequences",
          description: "List all sequences in the current project with basic info",
          inputSchema: {
            type: "object", 
            properties: {},
            required: []
          }
        },
        {
          name: "get_sequence_details",
          description: "Get detailed information about a specific sequence including tracks, effects, and markers",
          inputSchema: {
            type: "object",
            properties: {
              sequence_name: {
                type: "string",
                description: "Name of the sequence to get details for"
              }
            },
            required: ["sequence_name"]
          }
        },
        {
          name: "get_timeline_structure",
          description: "Get the track structure of the active sequence",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_timeline_clips", 
          description: "Get all clips in the active sequence with detailed information",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_project_media",
          description: "Get all media items in the project browser with file information",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_project_bins",
          description: "Get project bin structure and organization",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_playhead_info",
          description: "Get current playhead position and playback state",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_selection_info",
          description: "Get information about currently selected clips or time range",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_export_presets",
          description: "Get available export presets and their settings",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "get_render_queue",
          description: "Get current render queue status and items",
          inputSchema: {
            type: "object",
            properties: {},
            required: []
          }
        },
        {
          name: "trim_clip_by_frames",
          description: "Trim or extend the in/out point of a video or audio clip by a number of frames.",
          inputSchema: {
            type: "object",
            properties: {
              sequenceId: { type: "number", description: "Index of the sequence (0-based)" },
              clipId: { type: "string", description: "ID of the clip to trim" },
              framesDelta: { type: "number", description: "Number of frames to trim (positive or negative)" },
              direction: { type: "string", enum: ["in", "out"], description: "Which edit point to trim ('in' or 'out')" },
              trackType: { type: "string", enum: ["video", "audio"], description: "Track type ('video' or 'audio')" }
            },
            required: ["sequenceId", "clipId", "framesDelta", "direction", "trackType"]
          }
        },
        {
          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'],
          },
        },
        {
          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'],
          },
        },
      ];
    
      return {
        tools,
      };
    });
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 this is a read operation ('Get'), implying it's non-destructive, but doesn't disclose behavioral traits such as error handling (e.g., if sequence doesn't exist), performance considerations, or the format/structure of the returned information. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 front-loads the core purpose without unnecessary words. Every part earns its place by specifying the action, target, and included details, making it easy to parse and understand 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's moderate complexity (fetching detailed sequence info), lack of annotations, and no output schema, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, usage context, or return values. Without annotations or output schema, more completeness would be beneficial, but it meets a bare minimum for a read operation.

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%, with the single parameter 'sequence_name' fully documented in the schema. The description adds no additional meaning beyond what the schema providesβ€”it doesn't explain what constitutes a valid sequence name, provide examples, or clarify semantics. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

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 the resource 'detailed information about a specific sequence', specifying the types of information included (tracks, effects, and markers). It distinguishes this from siblings like 'list_all_sequences' by focusing on details for a single sequence, but doesn't explicitly contrast with similar tools like 'get_active_sequence_info' or 'get_timeline_structure'.

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, differentiate from siblings like 'get_active_sequence_info' (which might fetch current sequence) or 'get_timeline_structure' (which could overlap in scope), or indicate any constraints beyond needing a sequence name.

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