Skip to main content
Glama

get_timeline_clips

Retrieve all video and audio clips from the active Premiere Pro timeline with detailed metadata for editing, analysis, or automation workflows.

Instructions

Get all clips in the active sequence with detailed information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'get_timeline_clips' tool. It fetches clip data from a local HTTP server (port 3001), processes it, limits to first 20 clips, formats a detailed list with track info, timings, source paths, speed, and effects, and returns it as a formatted text response. Handles errors appropriately.
    async getTimelineClips() {
      try {
        const response = await fetch('http://localhost:3001/api/timeline-clips');
        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 clipsList = data.clips.slice(0, 20).map(clip => 
          `• **${clip.clip_name}** (${clip.track_type}${clip.track_number})\n  📍 ${clip.timeline_in} → ${clip.timeline_out} (${clip.duration})\n  📁 ${clip.source_file_path.split('\\').pop()}\n  ⚡ ${clip.speed}% ${clip.effects.length > 0 ? `| Effects: ${clip.effects.join(', ')}` : ''}`
        ).join('\n\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `🎬 **Timeline Clips (${data.total_clips} total${data.total_clips > 20 ? ', showing first 20' : ''})**\n\n${clipsList}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get timeline clips**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • mcp-server.js:237-238 (registration)
    Registration in the tool dispatcher switch statement within the CallToolRequestSchema handler, which routes calls to the getTimelineClips method.
    case 'get_timeline_clips':
      return await this.getTimelineClips();
  • Tool registration entry in the ListToolsRequestSchema handler, including the tool name, description, and input schema (empty object, no parameters required).
    {
      name: "get_timeline_clips", 
      description: "Get all clips in the active sequence with detailed information",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:83-91 (registration)
    The tool is registered here in the list of available tools returned by listTools.
    {
      name: "get_timeline_clips", 
      description: "Get all clips in the active sequence with detailed information",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
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 the tool retrieves clips with 'detailed information,' but doesn't specify what details are included, whether it's read-only, if it requires specific permissions, or how it handles errors. 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 function without unnecessary words. It's front-loaded and wastes no space, making it highly concise and well-structured.

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 has no parameters, no annotations, and no output schema, the description is minimally adequate but incomplete. It specifies what is retrieved but lacks details on the return format, error handling, or dependencies, which are important for a tool that likely interacts with a sequence state.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, which is acceptable here, but it could have clarified implicit context (e.g., that it operates on the current active sequence). Baseline is 4 for zero parameters.

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 target resource ('all clips in the active sequence'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_sequence_details' or 'get_timeline_structure', which might also retrieve sequence-related information, so it misses full sibling 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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an active sequence), exclusions, or compare to siblings like 'get_sequence_details' or 'get_selection_info', leaving usage context 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/jordanl61/premiere-pro-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server