English | 日本語 | Tiếng Việt | 简体中文 | 繁體中文 | 한국어 | Deutsch | Español | Français | Italiano | Dansk | Polski | Русский | Bosanski | العربية | Norsk | Português (Brasil) | ไทย | Türkçe | ភាសាខ្មែរ
Controla Adobe Premiere Pro a través de MCP usando Codex, Claude Code, Claude Desktop o cualquier otro cliente MCP.
¿Quieres algo construido desde cero para agentes de IA? Adobe sigue siendo potente, pero no es "AI-first". Ahora estoy creando Monet, un editor de vídeo diseñado desde el primer día para ser controlado totalmente por agentes de codificación.
Si buscas el camino nativo para IA, usa Monet. Si necesitas Adobe Premiere Pro hoy mismo, este proyecto sigue siendo para ti.
Interfaz de usuario del panel CEP actual dentro de Premiere Pro, utilizando los controles del puente renovados y el diseño de estado.
Related MCP server: Premiere-Pro-MCP
Este repositorio está validado actualmente para:
macOS
Adobe Premiere Pro 2020+ (usado y probado activamente en Premiere Pro 26.0)
Node.js 18+
la ruta del instalador de macOS incluida para Claude Desktop
registro manual de MCP para Codex, Claude Code y clientes MCP similares
Validación local actual a fecha de 4 de marzo de 2026:
97 herramientas expuestas
43 herramientas ejecutadas en vivo contra una sesión real de Premiere
50 herramientas validadas por esquema en el mismo barrido
3 herramientas destructivas sin argumentos fueron omitidas intencionalmente (save_project, undo, consolidate_duplicates)
1 limitación de tiempo de ejecución en vivo permanece: get_render_queue_status requiere integración con Adobe Media Encoder
La salida completa del barrido en vivo se escribe en /tmp/premiere-mcp-bridge/live-tool-sweep.json cuando ejecutas el verificador.
El servidor cubre operaciones de proyecto, ingesta, creación de secuencias, edición de línea de tiempo, transiciones, efectos, fotogramas clave, metadatos, exportaciones y flujos de trabajo de ensamblaje de alto nivel.
Ejemplos de prompts:
"Enumera todas las secuencias y muéstrame cuál está activa."
"Importa estos tres planos y construye un spot de producto preliminar."
"Añade disolvencias cruzadas a cada corte en la pista de vídeo 1."
"Aplica Desenfoque Gaussiano al clip central."
"Aplica el efecto Black & White al clip de formato corto activo."
"Corta la secuencia de la entrevista en el segundo 12.5 en todas las pistas de audio y vídeo."
"Exporta la secuencia activa como FCP XML."
Para estilos monocromáticos, prefiere apply_effect con Black & White en lugar de intentar forzar el blanco y negro mediante ajustes genéricos de saturación.
Antes de editar, también puedes adjuntar el recurso premiere://config/get_instructions para dar al modelo una guía operativa específica de Premiere.
Herramientas de flujo de trabajo de alto nivel incluidas:
build_motion_graphics_demo
assemble_product_spot
build_brand_spot_from_mogrt_and_assets
assemble_product_spot y build_brand_spot_from_mogrt_and_assets ahora admiten un argumento opcional clipPlan para que un LLM pueda dirigir la temporización por clip, la colocación en pista, las transiciones, el movimiento, los recortes, los efectos y los ajustes de color en lugar de depender de valores predeterminados de plantilla fijos.
git clone https://github.com/hetpatel-11/Adobe_Premiere_Pro_MCP.git
cd Adobe_Premiere_Pro_MCP
npm run setup:macEse instalador hará lo siguiente:
instalar dependencias
compilar dist/index.js
habilitar el modo de depuración de Adobe CEP
instalar la extensión MCP Bridge (CEP)
crear /tmp/premiere-mcp-bridge
añadir la entrada MCP premiere-pro a Claude Desktop
Importante:
el puente de interfaz de usuario compatible en este repositorio es la extensión MCP Bridge (CEP)
el instalador habilita automáticamente el modo de depuración de Adobe CEP
si Premiere no expone la extensión correctamente en tu máquina, habilita UXP Plugins > Enable developer mode en las preferencias de Premiere Pro antes de abrir el panel del puente
npm run setup:mac es la ruta más sencilla para Claude Desktop en macOS porque actualiza la configuración de Claude Desktop automáticamente
Después de que el instalador termine:
Cierra y vuelve a abrir tu cliente MCP si lee la configuración al iniciarse. Si usaste el instalador, eso significa Claude Desktop.
Cierra y vuelve a abrir Premiere Pro.
En Premiere Pro en macOS, abre Premiere Pro > Preferences > Plugins y habilita UXP Plugins > Enable developer mode.
Reinicia Premiere Pro si se cambió la configuración.
Abre Window > Extensions > MCP Bridge (CEP).
Establece Temp Directory en /tmp/premiere-mcp-bridge.
Haz clic en Save Configuration.
Haz clic en Start Bridge.
Conéctate desde Codex, Claude Code, Claude Desktop u otro cliente MCP usando el mismo directorio temporal.
Si los comandos fallan, haz clic en Run Diagnostics y envía /tmp/premiere-mcp-bridge/premiere-mcp-diagnostics-latest.json.
Si necesitas una referencia visual para el interruptor del modo de desarrollador, se ve así:
Si el panel informa que Premiere está listo después de Start Bridge, el puente está activo.
En macOS, usa:
npm run setup:macEsa es la única ruta en este repositorio que escribe automáticamente la entrada MCP por ti.
Compila el servidor primero:
npm install
npm run buildLuego añade el servidor MCP en una sola línea:
codex mcp add premiere_pro --env PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge -- node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.jsCompila el servidor de la misma manera:
npm install
npm run buildLuego registra el servidor MCP en Claude Code usando el mismo punto de entrada dist/index.js compilado y el mismo directorio temporal:
command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridgeSi usas un archivo de configuración MCP local en lugar de un comando auxiliar, apúntalo al mismo dist/index.js y establece la misma variable de entorno.
Usa el mismo enfoque de registro manual que Claude Code:
command: node /absolute/path/to/Adobe_Premiere_Pro_MCP/dist/index.js
env: PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridgeImportante para todas las configuraciones manuales de cliente:
mantén el comando en una sola línea
usa la ruta absoluta real a dist/index.js
reinicia el cliente después de añadir o actualizar la entrada MCP
inicia el puente CEP dentro de Premiere y confirma que el directorio temporal es exactamente /tmp/premiere-mcp-bridge
Ejecuta las comprobaciones integradas:
npm run setup:doctorEsto valida:
la versión de Node.js
la salida del servidor compilado
la instalación de la extensión CEP
/tmp/premiere-mcp-bridge
el modo de depuración de Adobe CEP
la entrada de configuración de Claude Desktop cuando usas la ruta del instalador
los diagnósticos del panel CEP escritos en /tmp/premiere-mcp-bridge/premiere-mcp-diagnostics-latest.json
Para una comprobación integral más profunda, usa un proyecto de Premiere desechable y ejecuta:
node scripts/live-tool-sweep.mjsEsto crea secuencias temporales Sweep ... en el proyecto abierto actualmente para que la cadena de herramientas se pruebe con datos reales.
+-----------+ +-----------+ +-----------+
| Client | MCP | Node.js | Files | CEP Panel |
| (Codex+) |<------>| MCP Server|<------>| (Premiere)|
+-----------+ +-----------+ +-----------+
|
v
+-----------+
| Premiere |
| DOM / QE |
+-----------+El cliente llama a una herramienta MCP.
El servidor Node genera ExtendScript más ayudantes compartidos.
El script se escribe en /tmp/premiere-mcp-bridge.
El panel CEP sondea ese directorio y ejecuta el script a través de CSInterface.evalScript().
El panel escribe el resultado de vuelta en el archivo de respuesta.
El servidor devuelve JSON estructurado al cliente MCP.
Las 97 herramientas expuestas se agrupan aproximadamente así:
Descubrimiento e inspección de proyectos
Gestión de proyectos y secuencias
Importación de medios y gestión de contenedores (bins)
Colocación en línea de tiempo y operaciones de clip
Efectos, transiciones, color y fotogramas clave
Marcadores, metadatos, etiquetas y control del área de trabajo
Ayudantes de exportación e intercambio
MOGRT, subtítulos, proxies y ayudantes de revinculación
Flujos de trabajo de ensamblaje de anuncios / promociones de alto nivel
Usa la introspección MCP en tu cliente para ver el catálogo completo de herramientas y los esquemas exactos.
Este proyecto es mucho más utilizable que el prototipo original, pero no es magia.
El scripting de Premiere todavía no expone todas las operaciones de la interfaz de usuario de forma limpia.
El diseño de títulos profesional todavía depende de activos MOGRT reales o flujos de trabajo gráficos externos.
get_render_queue_status solo es útil cuando la integración con Adobe Media Encoder está disponible.
Los mejores resultados provienen de metraje fuente real, audio real y activos de marca reales. La capa de automatización los ensambla y manipula; no reemplaza el criterio editorial.
Si las herramientas son visibles pero las llamadas fallan:
Confirma que Premiere Pro está abierto con un proyecto cargado.
Abre Window > Extensions > MCP Bridge (CEP).
Confirma que el directorio temporal es exactamente /tmp/premiere-mcp-bridge.
Haz clic en Start Bridge.
Si actualizaste el código del puente, haz clic derecho en el panel y elige Reload.
Reintenta el comando.
Si el cliente MCP no puede encontrar el servidor:
Verifica la ruta absoluta a dist/index.js.
Verifica PREMIERE_TEMP_DIR=/tmp/premiere-mcp-bridge.
Reinicia el cliente MCP después de cambiar la configuración.
Ejecuta npm run setup:doctor.
Comandos útiles:
npm run build
npm test -- --runInBand
npm run setup:doctor
node scripts/live-tool-sweep.mjsVer:
QUICKSTART.md para la ruta de instalación más corta
KNOWN_ISSUES.md para los límites actuales
CONTRIBUTING.md para el flujo de trabajo de desarrollo
Return the full JSON input schema for one Premiere tool name from search_tools. After reading it, call invoke_tool.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact tool name, e.g. trim_clip |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden of explaining behavior. It discloses that this tool only returns a schema and implies that it does not execute tools by instructing the agent to call invoke_tool afterward. It does not cover error cases, but for an introspection tool this is adequate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences provide the core behavior and the intended next action. There is no filler, repetition, or unnecessary detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter tool with no output schema, the description explains what is returned and how to continue the workflow. It could mention behavior for an invalid or unknown tool name, but the essential information for correct invocation is present.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema coverage is 100% and already documents the 'name' parameter with an example. The description adds only that the name should come from search_tools, which is helpful context but does not substantially enrich parameter understanding beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the resource: 'full JSON input schema for one Premiere tool name.' It also distinguishes the tool from siblings by tying it to search_tools and instructing that invoke_tool should come next.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description places the tool in a workflow: tool names come from search_tools, and after reading the schema the agent should call invoke_tool. It does not explicitly say when not to use this tool, but the sequential guidance is clear and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Run a Premiere tool by exact name. Use after search_tools. Hosts that only advertise the small always-on set cannot call trim_clip etc. as top-level MCP tools.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Exact tool name returned by search_tools | |
| arguments | No | Arguments for that tool |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full disclosure burden. It says 'Run a Premiere tool' but does not disclose that this is an arbitrary passthrough capable of side-effecting operations like trim_clip, nor does it mention error behavior when the tool name is invalid.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with the core purpose front-loaded. The host-limitation sentence is useful context but slightly jargon-heavy; still, every sentence earns its place and there is no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the key prerequisite ('Use after search_tools') and exact-name matching. However, it omits guidance on using get_tool_schema to fetch the target tool's argument schema, and gives no return/error expectations despite having no output schema or annotations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already documents both parameters: name is 'Exact tool name returned by search_tools' and arguments is 'Arguments for that tool'. The description reinforces exactness and ordering but does not add meaningful detail beyond the schema, such as how arguments should be structured per the target tool.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Run') with a specific resource ('a Premiere tool by exact name') and clarifies this is the generic execution entry point. Naming trim_clip and contrasting it with top-level MCP tools helps distinguish it from siblings like search_tools and get_tool_schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly says 'Use after search_tools', giving clear ordering guidance, and it explains the host limitation that makes invoke_tool necessary. However, it does not explicitly state when not to use this tool or mention alternatives like get_tool_schema for inspecting a tool's schema.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Lists all sequences in the current Premiere Pro project with their IDs, names, and basic properties.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
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 confirms the read-only, listing nature and names returned fields, but it's vague about 'basic properties' and omits edge-case behavior (empty project, no open document, performance on large projects).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with zero filler words. It states the action, scope, and result in one concise breath.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple 0-parameter listing tool, the description covers the essentials: scope ('all sequences in current project') and return shape (IDs, names, basic properties). The primary gap is the undefined 'basic properties' term, which matters more because there's no output schema to compensate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters, the schema carries no semantics, so per the rubric the baseline is 4. The description appropriately spends its space explaining the return value instead, which is the only useful thing it could add.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb-resource-scope structure ('Lists all sequences in the current Premiere Pro project') and specifies the return payload (IDs, names, basic properties). It distinguishes itself from list_project_items naturally, though 'basic properties' is undefined and it doesn't explicitly disambiguate from get_sequence_structure/get_full_sequence_info.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool vs. the many siblings such as list_sequence_tracks, get_full_sequence_info, or get_sequence_structure. There are no exclusions, prerequisites, or alternative suggestions — a missed opportunity given the crowded sibling space.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search the Premiere tool catalog with a BM25 natural-language query or a regex pattern, then call invoke_tool. Use this instead of expecting 280 editing tools in the MCP tool list. Empty query lists categories. Default 5 matches.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max matches, 1-25. Defaults to 5. | |
| query | No | Natural language BM25 query, e.g. "trim clip duration" or "export sequence" | |
| detail | No | How much of each match to return. schema includes the JSON input schema. Defaults to descriptions. | |
| pattern | No | Case-insensitive regex over tool name, description, category, and argument names. e.g. "^list_" or "mogrt" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden of behavioral disclosure. It discloses several concrete behaviors: empty query lists categories, default 5 matches, and dual support for BM25 and regex searches. It does not explicitly state read-only status or output format, but for a search operation the disclosed behaviors provide meaningful transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is four short sentences with no filler: purpose, usage instruction, empty-query behavior, and default limit. The critical 'use this instead' guidance is front-loaded, and every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and four optional parameters, the description covers tool selection rationale, query modes, the follow-up action, and important default/empty-query behavior. It does not specify the return shape, but the detail parameter schema fills that gap. This is sufficient for an agent to invoke the tool correctly in most cases.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that query and regex are alternative search modes and by revealing that an empty query produces categories—information not present in the schema. It repeats the default limit, but the added empty-query behavior justifies a score above baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb-resource pair ('Search the Premiere tool catalog') and names two concrete query mechanisms (BM25 natural-language or regex). It clearly differentiates this from siblings like invoke_tool and get_tool_schema, and the reference to the 280-tool MCP list explains its role as a discovery tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly instructs the agent to use this tool instead of expecting the full 280-tool MCP list, which is direct when-to-use guidance. It also tells the agent to follow up by calling invoke_tool, linking the search step to the execution step. While it doesn't enumerate exclusions in detail, the 'use this instead' phrasing is strong and actionable.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Readiness check for Premiere Pro and the MCP Bridge. Call this before any editing tool. If Premiere is installed and not running, this launches it and waits for the CEP panel, which auto-starts the bridge. If it fails, tell the user the nextStep and do not retry other tools.
| Name | Required | Description | Default |
|---|---|---|---|
| launchIfNeeded | No | When true (the default), launch Premiere if it is installed and the bridge heartbeat is missing. Set false for a check that never starts the app. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, and it does well: it reveals that the tool may launch Premiere as a side effect, waits for the CEP panel, auto-starts the bridge, and exposes nextStep on failure. It does not describe the exact return shape or success/failure indicators, which would make it fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, each earning its place: purpose, behavior/wait semantics, and failure handling. The most important instruction ('call before any editing tool') is front-loaded, and there is zero filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter check tool with no annotations and no output schema, the description is complete: what it does, when to call it, what side effects it may trigger, and how to handle failure. The 'nextStep' reference even hints at the failure return shape. An agent has everything needed to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%; the schema already fully documents launchIfNeeded including its default behavior and false-case meaning. The description refers to launching behavior but does not add parameter-level meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: a 'readiness check' for Premiere Pro and the MCP Bridge. It also frames itself as a prerequisite ('Call this before any editing tool'), which distinguishes it from the editing tools it precedes. The purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Provides explicit when-to-use guidance ('Call this before any editing tool') and when-not-to-continue guidance ('If it fails... do not retry other tools'). It names the class of alternatives (editing tools) and instructs the agent to surface nextStep to the user instead. This is unusually actionable usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v1.2.7add_adjustment_layeradd_audio_keyframesadd_custom_metadata_fieldadd_keyframeadd_markeradd_marker_to_project_itemadd_text_overlayadd_to_render_queueadd_to_timelineadd_to_timeline_batchadd_trackadd_tracksadd_transitionadd_transition_to_clipadjust_audio_levelsapply_audio_effectapply_audio_effect_to_all_clipsapply_effectapply_lutassemble_product_spotattach_custom_propertyauto_reframe_sequencebatch_add_transitionsbatch_apply_effectbatch_enable_disablebatch_rename_clipsbuild_brand_spot_from_mogrt_and_assetsbuild_motion_graphics_democapture_framecheck_offline_mediaclear_item_in_outclear_sequence_in_outclose_all_source_clipsclose_projectclose_sequenceclose_source_monitorcolor_correctconsolidate_and_transferconsolidate_duplicatescopy_effect_valuescopy_effects_between_clipscreate_bars_and_tonecreate_bincreate_caption_trackcreate_projectcreate_sequencecreate_sequence_from_clipscreate_sequence_from_presetcreate_smart_bincreate_subclipcreate_subsequencecrop_clipdelete_bindelete_markerdelete_multiple_project_itemsdelete_preview_filesdelete_project_itemdelete_sequencedelete_trackdeselect_all_clipsdetach_proxydetect_scene_editsdetect_silenceduplicate_clipduplicate_sequenceenable_disable_clipencode_fileencode_project_itemevaluate_expressionexecute_extendscriptexport_aafexport_as_fcp_xmlexport_as_projectexport_frameexport_omfexport_sequenceextract_selectionfind_items_by_media_pathfind_project_item_by_namefreeze_frameget_active_sequenceget_all_project_pathsget_bin_contentsget_capabilitiesget_clip_adjustment_layerget_clip_at_playheadget_clip_at_positionget_clip_linksget_clip_markersget_clip_propertiesget_clip_speedget_color_labelget_color_spaceget_duplicate_mediaget_effect_propertiesget_encoder_presetsget_export_file_extensionget_footage_interpretationget_full_clip_infoget_full_project_overviewget_full_sequence_infoget_graphics_white_luminanceget_insertion_binget_item_infoget_keyframesget_linked_itemsget_metadataget_mogrt_componentget_next_edit_pointget_offline_mediaget_playhead_positionget_premiere_stateget_project_infoget_project_item_infoget_project_panel_metadataget_project_scratch_disksget_qe_clip_infoget_render_queue_statusget_selected_clipsget_sequence_countget_sequence_in_out_pointsget_sequence_markers_by_typeget_sequence_settingsget_sequence_structureget_source_monitor_infoget_source_monitor_positionget_target_tracksget_timeline_gapsget_timeline_summaryget_tool_schemaget_total_clip_countget_track_infoget_unused_mediaget_used_media_reportget_value_at_timeget_version_infoget_work_areaget_workspacesget_xmp_metadatahas_proxyimport_edlimport_fcp_xmlimport_folderimport_image_sequenceimport_mediaimport_mogrtimport_mogrt_from_libraryimport_sequencesimport_sequences_from_projectinsert_from_sourceinspect_dom_objectinvert_selectioninvoke_toolis_work_area_enabledlift_selectionlink_audio_videolink_selectionlist_available_audio_effectslist_available_audio_transitionslist_available_effectslist_available_transitionslist_clip_effectslist_markerslist_project_itemslist_sequence_trackslock_trackmanage_proxiesmatch_framemove_clipmove_clip_to_trackmove_item_to_binmove_items_to_binmove_playhead_to_editmultiple_undomute_tracknest_clipsopen_in_sourceopen_projectoverwrite_clipoverwrite_from_sourcepingplay_source_monitorplay_timelinerazor_all_tracksrazor_timeline_at_timeread_sequence_captionsredorefresh_mediarelink_mediaremove_all_effectsremove_effectremove_effect_by_nameremove_from_timelineremove_keyframeremove_keyframe_rangeremove_selected_clipsrename_binrename_cliprename_project_itemrename_trackreplace_clipreplace_clip_mediareverse_clipripple_deleteroll_editsave_projectsave_project_asscene_edit_detectionsearch_project_itemssearch_toolsselect_all_clipsselect_clips_by_colorselect_clips_by_nameselect_clips_in_rangeselect_disabled_clipsselect_itemset_active_sequenceset_all_tracks_targetedset_anti_alias_qualityset_blend_modeset_clip_anchor_pointset_clip_opacityset_clip_panset_clip_positionset_clip_propertiesset_clip_properties_batchset_clip_rotationset_clip_scaleset_clip_selectionset_clip_speed_qeset_clip_start_timeset_clip_volumeset_color_labelset_color_valueset_effect_propertyset_footage_interpretationset_frame_blendset_graphics_white_luminanceset_item_in_outset_keyframe_interpolationset_metadataset_offlineset_override_frame_rateset_override_pixel_aspect_ratioset_playhead_positionset_poster_frameset_project_panel_metadataset_project_scratch_diskset_scale_to_frame_sizeset_scale_width_heightset_scratch_disk_pathset_sequence_audio_settingsset_sequence_display_formatset_sequence_field_typeset_sequence_frame_rateset_sequence_in_out_pointsset_sequence_pixel_aspect_ratioset_sequence_resolutionset_sequence_settingsset_source_in_outset_start_timeset_target_trackset_time_interpolationset_transcode_on_ingestset_uniform_scaleset_work_areaset_workspaceset_xmp_metadataset_zero_pointsetup_duckingslide_editslip_editspeed_changesplit_clipstabilize_clipstart_batch_encodestop_playbacktoggle_track_visibilitytrim_clipundounlink_selectionunnest_sequenceupdate_markervalidate_project_for_exportverify_premiere_connection1 field changedInput schema / properties / launchIfNeededAdded value: +{
+ "description": "When true (the default), launch Premiere if it is installed and the bridge heartbeat is missing. Set false for a check that never starts the app.",
+ "type": "boolean"
+}v1.2.0add_marker5 fields changedInput schema / properties / color / anyOfAdded value: +[
+ {
+ "enum": [
+ "green",
+ "red",
+ "purple",
+ "orange",
+ "yellow",
+ "white",
+ "blue",
+ "cyan"
+ ],
+ "type": "string"
+ },
+ {
+ "maximum": 7,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "pattern": "^[0-7]$",
+ "type": "string"
+ }
+]Input schema / properties / color / descriptionPrevious value: -"Marker color (e.g., \"red\", \"green\", \"blue\")"New value: +"Marker colour — a name (green, red, purple, orange, yellow, white, blue, cyan) or an index 0-7. Defaults to green."Input schema / properties / color / typeRemoved value: -"string"Input schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence to add the marker to"New value: +"The sequence ID (GUID) to add the marker to, as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1delete_marker3 fields changedInput schema / properties / markerId / minLengthAdded value: +1Input schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1delete_track2 fields changedInput schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1list_markers2 fields changedInput schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1list_sequence_tracks2 fields changedInput schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence to list tracks for"New value: +"The sequence ID (GUID) to list tracks for, as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1lock_track2 fields changedInput schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1move_clip1 field changedInput schema / properties / newTrackIndexRemoved value: -{
- "description": "The new track index (if moving to different track)",
- "type": "number"
-}set_sequence_settings6 fields changedInput schema / properties / settings / properties / frameRate / descriptionPrevious value: -"Frame rate"New value: +"Frames per second, e.g. 23.976, 25, 30"Input schema / properties / settings / properties / height / descriptionPrevious value: -"Frame height"New value: +"Frame height in pixels"Input schema / properties / settings / properties / pixelAspectRatio / anyOfAdded value: +[
+ {
+ "type": "number"
+ },
+ {
+ "type": "string"
+ }
+]Input schema / properties / settings / properties / pixelAspectRatio / descriptionPrevious value: -"Pixel aspect ratio"New value: +"Pixel aspect ratio, either a number (1, 1.5, 2) or an \"N:M\" string (\"1:1\", \"4:3\", \"10:11\")"Input schema / properties / settings / properties / pixelAspectRatio / typeRemoved value: -"number"Input schema / properties / settings / properties / width / descriptionPrevious value: -"Frame width"New value: +"Frame width in pixels"toggle_track_visibility2 fields changedInput schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1update_marker6 fields changedInput schema / properties / color / anyOfAdded value: +[
+ {
+ "enum": [
+ "green",
+ "red",
+ "purple",
+ "orange",
+ "yellow",
+ "white",
+ "blue",
+ "cyan"
+ ],
+ "type": "string"
+ },
+ {
+ "maximum": 7,
+ "minimum": 0,
+ "type": "integer"
+ },
+ {
+ "pattern": "^[0-7]$",
+ "type": "string"
+ }
+]Input schema / properties / color / descriptionPrevious value: -"New color"New value: +"New colour. Marker colour — a name (green, red, purple, orange, yellow, white, blue, cyan) or an index 0-7. Defaults to green."Input schema / properties / color / typeRemoved value: -"string"Input schema / properties / markerId / minLengthAdded value: +1Input schema / properties / sequenceId / descriptionPrevious value: -"The ID of the sequence"New value: +"The sequence ID (GUID) as returned in the \"id\" field by list_sequences or get_active_sequence"Input schema / properties / sequenceId / minLengthAdded value: +1v1.1.6add_adjustment_layeradd_audio_keyframes1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"add_custom_metadata_fieldadd_keyframeadd_markeradd_marker_to_project_itemadd_shapeadd_text_overlay15 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / alignmentRemoved value: -{
- "description": "Text alignment",
- "enum": [
- "left",
- "center",
- "right"
- ],
- "type": "string"
-}Input schema / properties / colorRemoved value: -{
- "description": "The hex color code for the text, e.g., \"#FFFFFF\"",
- "type": "string"
-}Input schema / properties / duration / descriptionPrevious value: -"How long the text should remain on screen in seconds"New value: +"How long the text should remain on screen in seconds (best-effort; the MOGRT's natural duration may take precedence)"Input schema / properties / fontFamilyRemoved value: -{
- "description": "e.g., \"Arial\", \"Times New Roman\"",
- "type": "string"
-}Input schema / properties / fontSizeRemoved value: -{
- "description": "e.g., 48",
- "type": "number"
-}Input schema / properties / mogrtPathAdded value: +{
+ "description": "Absolute path to a .mogrt template file (required for text overlays)",
+ "type": "string"
+}Input schema / properties / positionRemoved value: -{
- "additionalProperties": false,
- "description": "Text position on screen",
- "properties": {
- "x": {
- "description": "Horizontal position (0-100)",
- "type": "number"
- },
- "y": {
- "description": "Vertical position (0-100)",
- "type": "number"
- }
- },
- "type": "object"
-}Input schema / properties / rollbackOnTextFailureAdded value: +{
+ "description": "If true, remove the imported timeline Graphic when every requested text write fails. Defaults to false; the imported project item may remain in the Project panel.",
+ "type": "boolean"
+}Input schema / properties / text / descriptionPrevious value: -"The text content to display"New value: +"Text for the first AE text component in the MOGRT (typically the main title)"Input schema / properties / text2Added value: +{
+ "description": "Text for the second AE text component (e.g., subtitle of a lower third)",
+ "type": "string"
+}Input schema / properties / text3Added value: +{
+ "description": "Text for the third AE text component (if present)",
+ "type": "string"
+}Input schema / properties / text4Added value: +{
+ "description": "Text for the fourth AE text component (if present)",
+ "type": "string"
+}Input schema / properties / textPropertyNameAdded value: +{
+ "description": "Override: explicit displayName of the property to write into. When set, only `text` is written (text2/text3/text4 are ignored) and the call fails if no property with that displayName exists. Use only when auto-detection picks the wrong field.",
+ "type": "string"
+}Input schema / properties / trackIndex / descriptionPrevious value: -"The video track to place the text on"New value: +"The video track to place the text on (0-indexed; create the track first via add_track if needed)"add_to_render_queueadd_to_timeline4 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / linkAudioAdded value: +{
+ "description": "When false, removes the auto-linked audio counterpart that Premiere places on audio tracks for video-track clips. Useful for video overlays whose source media (e.g. Remotion .mov outputs) carry silent PCM that would overwrite existing audio. Default true (preserves Premiere's native linking behavior).",
+ "type": "boolean"
+}Input schema / properties / sourceInPointAdded value: +{
+ "description": "Source IN point in seconds — the start of the sub-range to pull from the source (footage or sequence). Replicates marking an in point in the Source monitor. Requires sourceOutPoint. When omitted, the whole source (or its current marks) is placed.",
+ "type": "number"
+}Input schema / properties / sourceOutPointAdded value: +{
+ "description": "Source OUT point in seconds — the end of the sub-range to pull from the source. Replicates marking an out point in the Source monitor. Requires sourceInPoint.",
+ "type": "number"
+}add_to_timeline_batchadd_trackadd_tracksadd_transition1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"add_transition_to_clip1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"adjust_audio_levels1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"apply_audio_effectapply_audio_effect_to_all_clipsapply_effect2 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / parameters / propertyNamesAdded value: +{
+ "type": "string"
+}apply_lut1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"assemble_product_spotattach_custom_propertyauto_edit_to_musicauto_reframe_sequencebatch_add_transitionsbatch_apply_effectbatch_enable_disablebatch_rename_clipsbuild_brand_spot_from_mogrt_and_assetsbuild_motion_graphics_democapture_framecheck_offline_mediaclear_item_in_outclear_sequence_in_outclose_all_source_clipsclose_projectclose_sequenceclose_source_monitorcolor_correct1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"consolidate_and_transferconsolidate_duplicatescopy_effect_valuescopy_effects_between_clipscreate_bars_and_tonecreate_bin1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"create_caption_trackcreate_multicam_sequencecreate_project1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"create_proxy_mediacreate_sequence7 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / frameRateRemoved value: -{
- "description": "Frame rate (e.g., 24, 25, 30, 60)",
- "type": "number"
-}Input schema / properties / heightRemoved value: -{
- "description": "Sequence height in pixels",
- "type": "number"
-}Input schema / properties / presetPath / descriptionPrevious value: -"Optional path to a sequence preset file for custom settings"New value: +"Absolute path to an installed Premiere .sqpreset sequence preset. Required so Premiere does not show the native New Sequence dialog."Input schema / properties / sampleRateRemoved value: -{
- "description": "Audio sample rate (e.g., 48000)",
- "type": "number"
-}Input schema / properties / widthRemoved value: -{
- "description": "Sequence width in pixels",
- "type": "number"
-}Input schema / requiredPrevious value: -[
- "name"
-]New value: +[
+ "name",
+ "presetPath"
+]create_sequence_from_clipscreate_sequence_from_presetcreate_smart_bincreate_subclipcreate_subsequencecrop_clipdelete_bindelete_markerdelete_multiple_project_itemsdelete_preview_filesdelete_project_itemdelete_sequence1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"delete_trackdeselect_all_clipsdetach_proxydetect_scene_editsdetect_silenceduplicate_clipduplicate_sequence2 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / clearContentsAdded value: +{
+ "description": "When true, remove all clips from the copy so it is empty but keeps the source's frame rate/resolution/track layout. Default false (full copy).",
+ "type": "boolean"
+}enable_disable_clipencode_fileencode_project_itemevaluate_expressionexecute_extendscriptexport_aafexport_as_fcp_xmlexport_as_projectexport_frame1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"export_omfexport_sequence9 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / allowOverwriteAdded value: +{
+ "description": "Allow writing to an existing output file. Defaults to false.",
+ "type": "boolean"
+}Input schema / properties / format / descriptionPrevious value: -"The export format or codec"New value: +"Deprecated hint only; the .epr preset controls codec/container."Input schema / properties / presetNameAdded value: +{
+ "description": "Exact user preset display name or filename stem. Must resolve to exactly one discovered .epr preset.",
+ "type": "string"
+}Input schema / properties / presetPath / descriptionPrevious value: -"Optional path to an export preset file (.epr) for specific settings"New value: +"Absolute path to an export preset file (.epr). Required unless presetName uniquely resolves through get_encoder_presets."Input schema / properties / quality / descriptionPrevious value: -"Export quality setting"New value: +"Deprecated hint only; the .epr preset controls quality."Input schema / properties / removeOnCompletionAdded value: +{
+ "description": "Pass AME removeOnCompletion. Defaults to true to preserve existing queue behavior.",
+ "type": "boolean"
+}Input schema / properties / resolution / descriptionPrevious value: -"Export resolution (e.g., \"1920x1080\", \"3840x2160\")"New value: +"Deprecated hint only; the .epr preset controls resolution."Input schema / properties / sourceRangeAdded value: +{
+ "description": "Export source range. Defaults to entire. Requested ranges are never silently substituted.",
+ "enum": [
+ "entire",
+ "in_out",
+ "work_area"
+ ],
+ "type": "string"
+}extract_selectionfind_items_by_media_pathfind_project_item_by_namefreeze_frameget_active_sequenceget_all_project_pathsget_bin_contentsget_capabilitiesget_clip_adjustment_layerget_clip_at_playheadget_clip_at_positionget_clip_linksget_clip_markersget_clip_propertiesget_clip_speedget_color_labelget_color_spaceget_duplicate_mediaget_effect_propertiesget_encoder_presetsget_export_file_extensionget_footage_interpretationget_full_clip_infoget_full_project_overviewget_full_sequence_infoget_graphics_white_luminanceget_insertion_binget_item_infoget_keyframesget_linked_itemsget_metadataget_mogrt_componentget_next_edit_pointget_offline_mediaget_playhead_positionget_premiere_stateget_project_info1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"get_project_item_infoget_project_panel_metadataget_project_scratch_disksget_qe_clip_infoget_render_queue_statusget_selected_clipsget_sequence_countget_sequence_in_out_pointsget_sequence_markers_by_typeget_sequence_settingsget_sequence_structureget_source_monitor_infoget_source_monitor_positionget_target_tracksget_timeline_gapsget_timeline_summaryget_total_clip_countget_track_infoget_unused_mediaget_used_media_reportget_value_at_timeget_version_infoget_work_areaget_workspacesget_xmp_metadatahas_proxyimport_edlimport_fcp_xmlimport_folder1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"import_image_sequenceimport_media1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"import_mogrtimport_mogrt_from_libraryimport_sequencesimport_sequences_from_projectinsert_from_sourceinspect_dom_objectinvert_selectionis_work_area_enabledlift_selectionlink_audio_videolink_selectionlist_available_audio_effectslist_available_audio_transitionslist_available_effectslist_available_transitionslist_clip_effectslist_markerslist_project_items1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"list_sequence_tracks1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"list_sequences1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"lock_trackmanage_proxiesmatch_framemove_clip1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"move_clip_to_trackmove_item_to_binmove_items_to_binmove_playhead_to_editmultiple_undomute_track1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"nest_clipsopen_in_sourceopen_project1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"overwrite_clipoverwrite_from_sourcepingplay_source_monitorplay_timelinerazor_all_tracksrazor_timeline_at_timeread_sequence_captionsredorefresh_mediarelink_mediaremove_all_effectsremove_effect5 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / additionalPropertiesPrevious value: -falseNew value: +{}Input schema / propertiesRemoved value: -{
- "clipId": {
- "description": "The ID of the clip",
- "type": "string"
- },
- "effectName": {
- "description": "The name of the effect to remove",
- "type": "string"
- }
-}Input schema / propertyNamesAdded value: +{
+ "type": "string"
+}Input schema / requiredRemoved value: -[
- "clipId",
- "effectName"
-]remove_effect_by_nameremove_from_timeline2 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / sequenceIdAdded value: +{
+ "description": "Optional sequence ID to search. If omitted, searches the active sequence first, then all sequences.",
+ "type": "string"
+}remove_keyframeremove_keyframe_rangeremove_selected_clipsrename_binrename_cliprename_project_itemrename_trackreplace_clipreplace_clip_mediareverse_clipripple_deleteroll_editsave_project1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"save_project_as1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"scene_edit_detectionsearch_project_itemsselect_all_clipsselect_clips_by_colorselect_clips_by_nameselect_clips_in_rangeselect_disabled_clipsselect_itemset_active_sequenceset_all_tracks_targetedset_anti_alias_qualityset_blend_modeset_clip_anchor_pointset_clip_opacityset_clip_panset_clip_positionset_clip_propertiesset_clip_properties_batchset_clip_rotationset_clip_scaleset_clip_selectionset_clip_speed_qeset_clip_start_timeset_clip_volumeset_color_labelset_color_valueset_effect_propertyset_footage_interpretationset_frame_blendset_graphics_white_luminanceset_item_in_outset_keyframe_interpolationset_metadataset_offlineset_override_frame_rateset_override_pixel_aspect_ratioset_playhead_positionset_poster_frameset_project_panel_metadataset_project_scratch_diskset_scale_to_frame_sizeset_scale_width_heightset_scratch_disk_pathset_sequence_audio_settingsset_sequence_display_formatset_sequence_field_typeset_sequence_frame_rateset_sequence_in_out_pointsset_sequence_pixel_aspect_ratioset_sequence_resolutionset_sequence_settingsset_source_in_outset_start_timeset_target_trackset_time_interpolationset_transcode_on_ingestset_uniform_scaleset_work_areaset_workspaceset_xmp_metadataset_zero_pointsetup_duckingslide_editslip_editspeed_change1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"split_clip1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"stabilize_clip1 field changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"start_batch_encodestop_playbacktoggle_track_visibilitytrim_clip3 fields changedInput schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / duration / descriptionPrevious value: -"Alternative: set the desired duration in seconds"New value: +"Alternative: set the desired timeline duration in seconds; cannot be combined with outPoint"Input schema / properties / outPoint / descriptionPrevious value: -"The new out point in seconds from the start of the clip"New value: +"The new out point in seconds from the start of the clip; cannot be combined with duration"undounlink_selectionunnest_sequenceupdate_markervalidate_project_for_exportverify_premiere_connectionadd_audio_keyframesadd_shapeadd_text_overlayadd_to_timelineadd_transitionadd_transition_to_clipadjust_audio_levelsapply_effectapply_lutauto_edit_to_musiccolor_correctcreate_bincreate_multicam_sequencecreate_projectcreate_proxy_mediacreate_sequencedelete_sequenceduplicate_sequenceexport_frameexport_sequenceget_project_infoimport_folderimport_medialist_project_itemslist_sequence_trackslist_sequencesmove_clipmute_trackopen_projectremove_effectremove_from_timelinesave_projectsave_project_asspeed_changesplit_clipstabilize_cliptrim_clipScored across 5 tools
Each tool occupies a distinct role in the bridge workflow: connection readiness, catalog search, schema lookup, tool invocation, and sequence listing. The search/schema/invoke tools form a clear sequence with explicit handoffs, so an agent should not confuse them.
All tool names follow lowercase snake_case with a verb_noun structure: verify_premiere_connection, search_tools, get_tool_schema, invoke_tool, list_sequences. There are no mixed conventions or vague overloaded verbs.
Five tools is well-scoped for a server that intentionally exposes a 280-tool catalog through a compact bridge layer rather than flooding the MCP tool list. Each tool is necessary for the discovery-and-invocation lifecycle.
The surface covers the full interaction loop: verify connection, search available tools, get a schema, invoke any cataloged tool, and list sequences directly. Since invoke_tool can execute any Premiere tool, there are no obvious missing operations for the server's stated purpose.
AI video editor for agents and humans: timeline, captions, color, audio and generation as MCP tools.
Edit video by talking to your AI — search footage, cut timelines, apply effects, add captions.
AI video editor: create projects, edit timelines, add captions and effects, and render videos.
Video production studio for AI agents: AI media, motion graphics as code, timeline and export.
