Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
get_project_infoB

Get basic information about the current Premiere Pro project

get_active_sequence_infoB

Get detailed information about the currently active sequence

list_all_sequencesB

List all sequences in the current project with basic info

get_sequence_detailsB

Get detailed information about a specific sequence including tracks, effects, and markers

get_timeline_structureB

Get the track structure of the active sequence

get_timeline_clipsB

Get all clips in the active sequence with detailed information

get_project_mediaB

Get all media items in the project browser with file information

get_project_binsB

Get project bin structure and organization

get_playhead_infoB

Get current playhead position and playback state

get_selection_infoB

Get information about currently selected clips or time range

get_export_presetsB

Get available export presets and their settings

get_render_queueB

Get current render queue status and items

trim_clip_by_framesC

Trim or extend the in/out point of a video or audio clip by a number of frames.

create_sequenceC

Create a new sequence in Premiere Pro

export_projectC

Export the current project or sequence

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 15 tools

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between 'get_active_sequence_info' and 'get_sequence_details' which could cause confusion. Additionally, 'get_timeline_clips' and 'get_timeline_structure' are closely related but serve different enough functions. Overall, the tools are well-differentiated with only minor ambiguities.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with clear, descriptive names. The naming convention is uniform throughout, using snake_case and starting with verbs like 'create', 'get', 'list', 'export', and 'trim'. This predictability makes it easy for agents to understand and select tools.

Tool Count5/5

With 15 tools, the server is well-scoped for a Premiere Pro integration, covering essential editing, project management, and export functions. Each tool appears to serve a specific and necessary purpose without redundancy, making the count appropriate for the domain's complexity.

Completeness4/5

The tool set provides strong coverage for reading project data, sequences, and media, as well as basic operations like creating sequences, trimming clips, and exporting. However, there are minor gaps, such as the lack of tools for adding effects, adjusting audio, or managing markers, which could limit advanced editing workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues