Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Clear Item In Out

clear_item_in_out

Remove in and out points from a Premiere Pro project item to reset it to its full duration.

Instructions

Clear in and/or out points on a project item (reset to full duration).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the project item
clear_inNoClear the in point (default: true)
clear_outNoClear the out point (default: true)

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

A4/5.0
Behavior4/5

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

Annotations already indicate this is a mutation (readOnlyHint=false) that is not flagged destructive. The description adds genuine behavioral context beyond annotations: the operation resets the item to full duration, explaining the semantic consequence of clearing points. It doesn't discuss reversibility or effects on existing sequences, but the core behavior is disclosed and there is no contradiction with annotations.

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 sentence with zero filler: verb, target, and outcome in one compact phrase. The behavioral clarification is delivered as a parenthetical that earns its place rather than padding the description.

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 simple 3-param boolean operation with an output schema and full schema coverage, the description captures the essential semantics. Minor gaps: it doesn't orient the agent toward the closely related set_item_in_out and clear_sequence_in_out siblings, and the definition of 'project item' is left to the schema. These are small omissions for a low-complexity tool.

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%, so the schema fully documents item_id, clear_in, and clear_out including defaults. The description adds the 'and/or' clarification and the 'reset to full duration' outcome, but no param-specific detail beyond what the schema already provides. Baseline 3 is appropriate when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (clear), a precise resource (in/out points on a project item), and the resulting state (reset to full duration). The parenthetical clarifies what 'clearing' actually means, and the phrase 'project item' distinguishes it from sequence-level siblings like clear_sequence_in_out and set_sequence_in_out_points.

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 resource scope ('on a project item') implies when the tool applies, and the sibling list contains sequence-level counterparts (clear_sequence_in_out, set_sequence_in_out_points) that an agent could infer are alternatives. However, no explicit routing, exclusions, or conditions are given — the agent must infer the boundaries between this tool and related item-level tools like set_item_in_out.

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