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

premiere-pro-mcp

by MauricePutinas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Send keystrokes/shortcut

premiere_send_shortcut

Send keyboard shortcuts to Adobe Premiere Pro by focusing the application and simulating keystrokes. Use for commands not covered by dedicated tools.

Instructions

ADVANCED FALLBACK: focus Premiere and send keystrokes (Windows SendKeys syntax, e.g. '^s' for Ctrl+S, '%{F4}' for Alt+F4). Use only when no dedicated tool exists. Premiere must be running.

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": {
      "keys": "<keys>"
    },
    "name": "premiere_send_shortcut"
  }
}

Input Schema

NameRequiredDescriptionDefault
keysYesSendKeys string, e.g. '^s' (Ctrl+S), '^+e' (Ctrl+Shift+E), '{ESC}'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Discloses that it focuses Premiere (potentially disruptive) and uses Windows SendKeys syntax. The 'ADVANCED FALLBACK' label implies unreliability. The openWorldHint annotation aligns with possible side effects. Minor gap: no mention of synchronous/asynchronous behavior or delays.

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 'ADVANCED FALLBACK', include prerequisite, syntax, and guidance. Every sentence adds essential information without waste.

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 fallback tool with one parameter and no output schema, the description provides adequate context: when to use, prerequisites, syntax. Lacks error behavior or what happens if Premiere is not focused, but these are minor for a fallback.

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?

Schema coverage is 100%, so baseline is 3. The description adds concrete syntax examples ('^s', '%{F4}', '{ESC}') that go beyond the generic schema description, helping the agent format the key string correctly.

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 tool focuses Premiere and sends keystrokes, with specific syntax examples ('^s' for Ctrl+S). It distinguishes itself from siblings by labeling as 'ADVANCED FALLBACK' and advising use only when no dedicated tool exists.

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

Usage Guidelines5/5

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

Explicitly states 'Use only when no dedicated tool exists' and includes prerequisite 'Premiere must be running.' This provides clear context for when to use this tool versus alternatives.

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