Skip to main content
Glama

get_project_info

Retrieve current Premiere Pro project details including name, settings, and metadata for workflow automation and AI integration.

Instructions

Get basic information about the current Premiere Pro project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that implements the core logic for the 'get_project_info' tool. It makes an HTTP request to localhost:3001 to retrieve project statistics from Premiere Pro and formats the response as MCP content or handles errors.
      async getProjectInfo() {
        try {
          // Fetch real project info from HTTP server which communicates with Premiere Pro
          const response = await fetch('http://localhost:3001/api/project-stats');
          if (!response.ok) {
            throw new Error(`HTTP ${response.status}: ${response.statusText}`);
          }
          
          const projectData = await response.json();
          
          return {
            content: [
              {
                type: 'text',
                text: `**Current Premiere Pro Project Information:**
    
    šŸ“½ļø **Project**: ${projectData.projectName || 'Unknown Project'}
    šŸŽ¬ **Sequences**: ${projectData.sequences || 0}
    šŸŽ„ **Clips**: ${projectData.clips || 0}
    šŸ“ **Bins**: ${projectData.bins || 0}  
    šŸ›¤ļø **Tracks**: ${projectData.tracks || 0}
    ā±ļø **Duration**: ${projectData.duration || 'Unknown'}
    
    *Retrieved from active Premiere Pro instance*`,
              },
            ],
          };
        } catch (error) {
          return {
            content: [
              {
                type: 'text',
                text: `āŒ **Error getting project info**: ${error.message}
    
    **Troubleshooting:**
    - Ensure Premiere Pro is running
    - Check that HTTP server is running on port 3001
    - Verify the MCP extension is loaded in Premiere Pro
    - Make sure a project is open in Premiere Pro`,
              },
            ],
            isError: true,
          };
        }
      }
  • The schema and metadata definition for the 'get_project_info' tool, including an empty input schema indicating no parameters are required.
    {
      name: "get_project_info",
      description: "Get basic information about the current Premiere Pro project",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • mcp-server.js:222-223 (registration)
    Registration of the tool in the CallToolRequestSchema handler's switch statement, dispatching calls to the getProjectInfo method.
    case 'get_project_info':
      return await this.getProjectInfo();
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 the action ('Get') but doesn't clarify if this is a read-only operation, what permissions might be needed, or how the information is returned (e.g., format, potential errors). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 purpose without any unnecessary words. It is front-loaded and efficiently conveys the essential information, 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 complete. It specifies the resource ('current Premiere Pro project') and action ('Get basic information'), but doesn't detail what 'basic information' includes or the return format, leaving gaps in context for an AI agent to fully understand the tool's behavior.

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 there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides, but it could hint at implicit context (e.g., 'current' project). Since there are no parameters, a baseline of 4 is appropriate, as the description adequately addresses the lack of inputs.

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 resource ('basic information about the current Premiere Pro project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_sequence_details' or 'get_project_bins', which also retrieve project-related information, 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 sibling tools like 'get_sequence_details' or 'get_project_media', there's no indication of what 'basic information' entails or when this tool is preferred over others, 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