Skip to main content
Glama

get_active_sequence_info

Retrieve detailed information about the currently active sequence in Adobe Premiere Pro for automation, querying, and workflow integration.

Instructions

Get detailed information about the currently active sequence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function implementing the 'get_active_sequence_info' tool. It fetches active sequence information from a local HTTP API endpoint and returns a formatted text response with details like name, duration, frame rate, resolution, tracks, etc. Includes comprehensive error handling.
    async getActiveSequenceInfo() {
      try {
        const response = await fetch('http://localhost:3001/api/active-sequence');
        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}\n\nšŸ”§ **Troubleshooting Steps:**\n1. Make sure Premiere Pro is running\n2. Open a project with an active sequence\n3. Ensure the CEP extension is loaded\n4. Click "Refresh Project Info" in the extension`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text', 
              text: `šŸŽ¬ **Active Sequence Details**\n\n**Name:** ${data.sequence_name}\n**Duration:** ${data.duration}\n**Frame Rate:** ${data.frame_rate} fps\n**Resolution:** ${data.resolution.width}x${data.resolution.height}\n**Audio Sample Rate:** ${data.audio_sample_rate} Hz\n**Timecode Start:** ${data.timecode_start}\n**Playhead Position:** ${data.playhead_position}\n**Video Tracks:** ${data.track_count.video_tracks}\n**Audio Tracks:** ${data.track_count.audio_tracks}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `āŒ **Failed to get active sequence info**\n\nError: ${error.message}\n\nšŸ”§ **Troubleshooting:**\n1. Check that the HTTP server is running on port 3001\n2. Ensure Premiere Pro is open with an active sequence\n3. Verify CEP extension is loaded and functional`,
            },
          ],
          isError: true,
        };
      }
    }
  • The tool schema definition returned by ListToolsRequestSchema, specifying the tool name, description, and empty input schema (no parameters required).
    {
      name: "get_active_sequence_info", 
      description: "Get detailed information about the currently active sequence",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:225-226 (registration)
    Tool registration/dispatch in the CallToolRequestSchema switch statement, routing calls to the getActiveSequenceInfo handler method.
    case 'get_active_sequence_info':
      return await this.getActiveSequenceInfo();
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 it 'gets' information, implying a read-only operation, but doesn't specify what 'detailed information' includes, whether it requires specific permissions, or how it handles edge cases (e.g., no active sequence). This leaves significant gaps in understanding the tool's 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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy for an AI agent 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 a tool that retrieves 'detailed information' about an active sequence, the description is incomplete. With no annotations, no output schema, and no details on what information is returned or how 'active' is defined, the agent lacks sufficient context to use this tool effectively compared to siblings.

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 the input schema has 100% description coverage (though empty). The description doesn't need to add parameter semantics, so it meets the baseline of 4 for tools with no parameters, as there's nothing to compensate for.

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 the currently active sequence', making the purpose understandable. However, it doesn't distinguish this tool from similar siblings like 'get_sequence_details' or 'list_all_sequences', which would require explicit differentiation to earn a 5.

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 like 'get_sequence_details' or 'get_playhead_info'. It mentions 'currently active sequence' but doesn't clarify what constitutes 'active' or whether there are prerequisites (e.g., a sequence must be open). This lack of contextual guidance limits its utility for an AI agent.

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