Skip to main content
Glama
Sign In
premiere-pro-mcp

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get logs

premiere_get_logs
Read-only

Read Adobe Premiere Pro log and diagnostic files to troubleshoot issues. Returns the tail of each log or full content of a specified file.

Instructions

Read Premiere's log/diagnostic files (Plugin Loading.log, Debug/Trace databases, logs folder). Returns the tail of each, or the full content of one file if 'file' is given. Read-only.

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": "premiere_get_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoAbsolute path of a single log file to read fully (bounded to 200 KB).
tailLinesNoLines from the end of each log (default 40).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations provide readOnlyHint=true. The description adds behavioral details: returns tails of multiple files or full content of one file if 'file' is given. No side effects are disclosed, but none are expected for a read-only operation.

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?

Two sentences, front-loaded with the core purpose, no filler. Every word adds value.

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?

The description explains what the tool returns (tail vs full file), which is sufficient given the simple parameter set and read-only nature. No output schema exists, so the description compensates reasonably.

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%, so baseline is 3. The description adds context about the 'file' parameter overriding the default tail behavior, but the schema already describes both parameters adequately.

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 specifies the tool reads Premiere's log/diagnostic files, lists example filenames, and distinguishes behavior (tail vs full file). As the only log-reading sibling, it is well-differentiated.

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 states 'Read-only', indicating a safe operation. While it doesn't explicitly contrast with sibling tools, no sibling overlaps in function, so it is clear enough for an agent to decide when to invoke.

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