Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

encode_file

Encodes a specified media file to a chosen format so you can prepare source assets for editing or delivery without leaving your Premiere Pro workflow.

Instructions

Premiere Pro expanded operation: encode file.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "encode_file"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

D1.8/5.0
Behavior1/5

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

Without any annotations, the description must disclose behavioral traits (e.g., side effects, output, limitations). It does none of this—'Premiere Pro expanded operation: encode file' reveals nothing about what the tool actually does, what it returns, or any side effects, constituting a complete lack of transparency.

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

Conciseness2/5

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

The description is extremely brief, but brevity here is not conciseness—it is under-specification. The single sentence adds no actionable information, making it unhelpful rather than efficient.

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

Completeness1/5

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

With no output schema, no annotations, no parameters, and a complex operation like encoding, the description is grossly incomplete. It fails to explain what file is encoded, what inputs are expected, what the outcome is, or how it relates to other encode/export tools, making it inadequate for an agent.

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

Parameters4/5

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

Since the tool has zero parameters (schema is empty), the baseline is 4. The description does not need to add parameter information, and indeed it does not, so it meets the baseline for this dimension.

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

Purpose2/5

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

The description states a generic action ('encode file') but provides no specifics about what 'expanded operation' means or how it differs from sibling tools like encode_project_item, export_sequence, or start_batch_encode. The verb-resource combination is clear only at a superficial level, lacking the scope and distinction needed for reliable tool selection.

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

Usage Guidelines1/5

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

No guidance is given on when to use this tool versus the many encoding/exporting siblings. There is no mention of prerequisites, expected input, or context in which 'expanded operation' applies, leaving the agent with zero usage direction.

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