Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Marker

delete_marker
Destructive

Delete a marker at any specified time position. Provide the time in seconds and optional clip node ID to remove the marker from the sequence or clip.

Instructions

Delete a marker at a specific time position

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
node_idNoOptional clip node ID (deletes from sequence if omitted)
time_secondsYesTime position of the marker to delete

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the tool completed successfully.
dataNoTool-specific result data when ok is true.
toolYesThe registered MCP tool name.
errorNoFailure detail when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Changed1 schema field changedv1.4.0
    • removedInput schema / additionalProperties
      Removed value: -false
  3. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description merely restates the destructive nature through the verb 'Delete' without adding behavioral context such as irreversibility, behavior when no marker exists at time_seconds, or consequences for dependent workflows. The description does not contradict the annotations, but it also adds no disclosure beyond what annotations already convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, tightly worded sentence with the action verb front-loaded and no filler. It is appropriately short, though it could earn a 5 if it packed in scope or usage guidance at the cost of only a few words.

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?

The output schema and annotations cover return values and destructive safety, and the input schema fully documents both parameters, so much of the burden is already carried by structured fields. The remaining gaps are usage context: no guidance on when deletion is appropriate versus updating a marker, and no caveat about the sequence-vs-clip scope beyond the node_id parameter description.

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%, with both time_seconds and node_id documented in the input schema, so the baseline of 3 applies. The description adds no meaning beyond the schema — 'at a specific time position' merely echoes the time_seconds parameter description, and it says nothing about node_id that the schema doesn't already cover.

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 states a specific verb ('Delete') and resource ('a marker') plus the identifying criterion ('at a specific time position'), which distinguishes it from marker siblings like add_marker, update_marker, and list_markers by action. However, it does not specify whether the marker lives on a sequence or a clip — that scope is left to the node_id parameter, so differentiation from sibling marker tools is incomplete.

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 gives no guidance on when to use this tool versus alternatives; it never mentions update_marker for modifying markers, list_markers for finding them, or the fact that omitting node_id deletes from the sequence while providing it deletes from a clip. The only usage hint lives in the node_id parameter description, not in the tool description itself.

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