Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Set Source In Out

set_source_in_out

Set in and out points on the clip currently open in the Source Monitor to define the exact edit range. Provide in_seconds, out_seconds, or both.

Instructions

Set in and/or out points on the clip currently open in the Source Monitor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
in_secondsNoIn point in seconds. Provide this, out_seconds, or both.
out_secondsNoOut point in seconds. Provide this, in_seconds, or both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.18.6
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / properties / data / description
      Previous value: -"Tool-specific result data when ok is true."New value: +"Tool-specific result data when ok is true; on failure, diagnostic detail when the tool provides it."
  2. Changed5 schema fields changedv1.18.0
    • addedInput schema / anyOf
      Added value: +[
+  {
+    "required": [
+      "in_seconds"
+    ]
+  },
+  {
+    "required": [
+      "out_seconds"
+    ]
+  }
+]
    • changedInput schema / properties / in_seconds / description
      Previous value: -"In point in seconds (optional)"New value: +"In point in seconds. Provide this, out_seconds, or both."
    • addedInput schema / properties / in_seconds / minimum
      Added value: +0
    • changedInput schema / properties / out_seconds / description
      Previous value: -"Out point in seconds (optional)"New value: +"Out point in seconds. Provide this, in_seconds, or both."
    • addedInput schema / properties / out_seconds / minimum
      Added value: +0
  3. Changed2 schema fields changedv1.14.4
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Tool-specific result data when ok is true."
+    },
+    "error": {
+      "description": "Failure detail when ok is false.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the tool completed successfully.",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "The registered MCP tool name.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  5. First observedv1.1.1

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare it is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds the useful precondition that a clip must be open in the Source Monitor, but says nothing about persistence, error behavior when no clip is open, or reset semantics.

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?

A single front-loaded sentence with no filler; the scope qualifier is placed after the verb+resource so the core action reads first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with an output schema and full annotation coverage, the description supplies the key missing context (the Source Monitor precondition) and correctly leaves return values to the output schema. Only error/edge-case behavior is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and each parameter already documents itself ('Provide this, out_seconds, or both'). The description's 'in and/or out' mirrors the anyOf constraint but adds no syntax, units, or format detail beyond the schema.

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?

States a specific verb (set), resource (in/out points), and scope (clip currently open in the Source Monitor), which cleanly separates it from set_sequence_in_out_points and set_item_in_out. It does not explicitly name those siblings, but the target object is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'currently open in the Source Monitor' implies the precondition for use, but there is no explicit when-to-use/when-not guidance or pointer to the sequence/item in-out siblings. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools