Skip to main content
Glama

get_project_media

Retrieve all media items from a Premiere Pro project browser with file details for automation, AI integration, and workflow management.

Instructions

Get all media items in the project browser with file information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that fetches project media data from the local HTTP server at localhost:3001/api/project-media, formats it into a readable list of media items (showing first 15 if many), including details like resolution, file size, bin location, usage, and offline status, and returns it as MCP content.
    async getProjectMedia() {
      try {
        const response = await fetch('http://localhost:3001/api/project-media');
        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 mediaList = data.media_items.slice(0, 15).map(media => 
          `• **${media.file_name}** (${media.duration})\n  📐 ${media.resolution.width}x${media.resolution.height} @ ${media.frame_rate}fps\n  💾 ${media.file_size_mb}MB | 🎵 ${media.audio_channels}ch @ ${media.audio_sample_rate}Hz\n  📁 ${media.bin_location} | Used: ${media.usage_count}x ${media.is_offline ? '❌ OFFLINE' : '✅'}`
        ).join('\n\n');
    
        return {
          content: [
            {
              type: 'text',
              text: `📁 **Project Media (${data.total_media_count} items${data.total_media_count > 15 ? ', showing first 15' : ''})**\n\n${mediaList}\n\n**Total Duration:** ${data.total_duration}\n**Offline Media:** ${data.offline_media_count} items`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `❌ **Failed to get project media**\n\nError: ${error.message}`,
            },
          ],
          isError: true,
        };
      }
    }
  • The tool schema definition in the ListTools response, specifying the name, description, and input schema (no required parameters).
    {
      name: "get_project_media",
      description: "Get all media items in the project browser with file information",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:240-241 (registration)
    Registration and dispatch of the tool in the CallToolRequestHandler switch statement, routing calls to the getProjectMedia handler method.
    case 'get_project_media':
      return await this.getProjectMedia();
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 it 'Get[s] all media items' but doesn't specify if this is a read-only operation, potential performance impacts, or any constraints like permissions or rate limits. This leaves significant gaps in understanding how the tool behaves.

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 that directly states the tool's function without unnecessary words. It's front-loaded and efficiently conveys the core purpose, 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 0 parameters, no annotations, and no output schema, the description is minimally adequate by stating what it does. However, it lacks details on behavioral traits, output format, or differentiation from siblings, making it incomplete for fully informed usage in a complex environment with many related tools.

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 parameter details, which is appropriate, but since there are no parameters, it doesn't fully compensate for any gaps, so it scores slightly below the maximum.

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 'all media items in the project browser with file information', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_project_bins' or 'get_timeline_clips', which might also retrieve media-related data, so it doesn't reach the highest score.

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. With siblings like 'get_project_bins' and 'get_timeline_clips' that might handle media in different contexts, there's no indication of when this tool is appropriate or what distinguishes it, leaving usage 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