Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

refresh_media

Reload a project item from its source file on disk to update stale media or reflect external changes in the Premiere Pro project.

Instructions

Refreshes the media for a project item, reloading it from disk.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectItemId": "<projectItemId>"
    },
    "name": "refresh_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectItemIdYesThe ID of the project item to refresh

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses the source of refresh (disk) but does not mention side effects, failure modes (e.g., file missing), or whether edits/proxies are affected. This is a basic disclosure but insufficient for a mutation tool without 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?

The description is one sentence with no fluff, efficiently conveying the core action and source. It is appropriately concise and front-loaded.

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 tool with one parameter, no output schema, and no annotations, the description is mostly complete. However, it could mention behavior when the file is missing or if it affects existing metadata, which would add robustness. Still, it adequately covers the essential purpose.

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 the sole parameter 'projectItemId' is adequately described in the schema. The description adds no new parameter-level detail, so the baseline of 3 is appropriate.

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 clearly states the action: 'Refreshes the media for a project item, reloading it from disk.' It specifies the verb (refresh) and the target (project item), and distinguishes from siblings like import_media or relink_media by the reload-from-disk intent.

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 description implies usage: when media may be out of sync with the disk or needs reloading. It does not explicitly name alternatives or exclusions, but the context is clear enough that an agent can infer when to use it. However, it could have explicitly pointed to relink_media or check_offline_media for alternative scenarios.

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