Skip to main content
Glama

get_timeline_structure

Retrieve the track structure of your active Premiere Pro sequence to analyze timeline organization and automate video editing workflows.

Instructions

Get the track structure of the active sequence

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_timeline_structure' tool. It fetches the timeline structure data from a local HTTP API (localhost:3001), processes video and audio tracks into a formatted text response, and handles errors.
    async getTimelineStructure() {
      try {
        const response = await fetch('http://localhost:3001/api/timeline-structure');
        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.video_tracks.map(track => 
          `  • V${track.track_index}: ${track.track_name} ${track.is_locked ? '🔒' : ''} ${track.is_visible ? '👁️' : '🙈'} (${track.blend_mode})`
        ).join('\n');
    
        const audioTracks = data.audio_tracks.map(track => 
          `  • A${track.track_index}: ${track.track_name} ${track.is_locked ? '🔒' : ''} ${track.is_muted ? '🔇' : '🔊'} ${track.is_solo ? '🎯' : ''} (Vol: ${track.volume}dB, Pan: ${track.pan})`
        ).join('\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎬 **Timeline Structure: ${data.sequence_name}**\n\n**Video Tracks:**\n${videoTracks}\n\n**Audio Tracks:**\n${audioTracks}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get timeline structure**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The tool schema definition including name, description, and empty input schema (no parameters required), provided in the ListTools response.
    {
      name: "get_timeline_structure",
      description: "Get the track structure of the active sequence",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:234-235 (registration)
    The switch case in the CallToolRequestHandler that registers and dispatches calls to the getTimelineStructure handler method.
    case 'get_timeline_structure':
      return await this.getTimelineStructure();
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves information ('Get'), implying a read-only operation, but doesn't disclose behavioral traits such as error conditions, performance considerations, or what 'track structure' entails (e.g., format, depth). This leaves gaps for a tool with no 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.

Conciseness5/5

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

The description is a single, clear sentence with no wasted words. It's front-loaded with the core purpose, making it highly efficient and easy to parse.

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 no annotations, no output schema, and the description's minimal detail, the tool is under-specified. It lacks information on return values, error handling, or context for 'active sequence' and 'track structure', making it incomplete for effective use despite its simplicity.

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%, so no parameter documentation is needed. The description doesn't add param info, but this is appropriate given the lack of inputs, earning a baseline score above 3 for simplicity.

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 ('Get') and the resource ('track structure of the active sequence'), making the purpose understandable. It doesn't explicitly differentiate from sibling tools like 'get_active_sequence_info' or 'get_sequence_details', but the specific focus on 'track structure' provides some distinction.

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. The description implies it operates on the 'active sequence', but it doesn't specify prerequisites (e.g., whether a sequence must be open) or compare it to siblings like 'get_sequence_details' or 'get_timeline_clips'.

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