Skip to main content
Glama

get_playhead_info

Retrieve the current playhead position and playback status in Adobe Premiere Pro for automation, monitoring, or integration purposes.

Instructions

Get current playhead position and playback state

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches playhead information from the local HTTP server at localhost:3001/api/playhead, processes the data, and returns formatted text response about playhead position, timecode, playback status, etc. Handles errors gracefully.
    async getPlayheadInfo() {
      try {
        const response = await fetch('http://localhost:3001/api/playhead');
        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}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text',
              text: `⏱️ **Playhead Info**\n\n**Sequence:** ${data.sequence_name}\n**Timecode:** ${data.timecode}\n**Frame:** ${data.frame_number}\n**Progress:** ${data.percentage_complete}%\n**Status:** ${data.is_playing ? '▶️ Playing' : '⏸️ Paused'}\n**Speed:** ${data.playback_speed}x`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get playhead info**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Tool definition in the listTools response, including name, description, and empty input schema (no parameters required).
    {
      name: "get_playhead_info",
      description: "Get current playhead position and playback state",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:246-247 (registration)
    Registration and dispatch in the tool call request handler switch statement, routing calls to the getPlayheadInfo handler method.
    case 'get_playhead_info':
      return await this.getPlayheadInfo();
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 of behavioral disclosure. It states what data is retrieved but doesn't describe traits like whether this is a read-only operation, if it requires specific permissions, latency considerations, or how it handles errors. For a tool with zero 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 with zero waste. It front-loads the core purpose ('Get current playhead position and playback state') without unnecessary details. Every word earns its place, making it easy for an agent to parse 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 simplicity (0 parameters, no output schema), the description is adequate but minimal. It covers the basic purpose but lacks context on usage, behavioral traits, or output format. Without annotations or output schema, the agent must rely on the description alone, which is incomplete for informed tool selection.

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 appropriately doesn't mention parameters, focusing instead on the tool's purpose. This aligns with the baseline expectation for parameterless tools, where the description needn't compensate for schema gaps.

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 tool's purpose with specific verbs ('Get') and resources ('current playhead position and playback state'). It distinguishes itself from siblings like 'get_active_sequence_info' or 'get_selection_info' by focusing on playhead-specific data. However, it doesn't explicitly differentiate from all siblings, such as 'get_sequence_details' which might also include playhead info.

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, context (e.g., during playback or editing), or exclusions. For example, it doesn't clarify if this is for real-time monitoring or static state retrieval, leaving the agent to infer usage from the tool name alone.

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