Skip to main content
Glama
leancoderkavy

Premiere Pro MCP Server

by leancoderkavy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Refresh Media

refresh_media

Reload project items to reflect changes made to source files in Premiere Pro.

Instructions

Refresh a project item to pick up changes to the source file

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_idYesNode ID or name of the item to refresh

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. Addedv1.4.0
  3. Removedv1.1.5
  4. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, so this is a mutating operation and the description carries some disclosure burden. It adds that the item's in-project state is re-synced from the source file, which is useful context. But it does not disclose side effects such as whether in-app modifications are lost or what happens when the source file is missing or offline. 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?

One 13-word sentence that front-loads the action ('Refresh a project item') and then gives the purpose. Zero filler and no redundancy with the title.

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 one-parameter tool with full schema coverage, an output schema, and safety annotations, the description covers what and why. The remaining gaps are minor: sibling-routing guidance (refresh vs. relink_media) and edge-case behavior for offline or missing source files. Nothing essential for a basic call is missing.

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 coverage is 100% and item_id is already documented as 'Node ID or name of the item to refresh', so the schema carries the parameter meaning. The description adds only slight disambiguation by clarifying the target is a project item rather than a clip or sequence. Baseline 3 applies because the schema does the heavy lifting.

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?

Uses a specific verb ('refresh') and resource ('project item') with a purpose clause ('to pick up changes to the source file') that goes beyond the title. This distinguishes it from nearby siblings: relink_media changes the source link, while check_offline_media only inspects status. An agent can tell what this tool does without opening the schema.

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

Usage Guidelines4/5

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

The phrase 'to pick up changes to the source file' provides an explicit trigger condition: use when the external source file changed on disk. However, no alternatives are named and there is no when-not-to-use guidance, even though relink_media, check_offline_media, and set_offline occupy the same problem space. The boundary between refresh and relink is left to inference.

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