Skip to main content
Glama
Sign In
MCP Premiere Pro

MCP Premiere Pro

by Miinwan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

proxy_status

Monitor proxy generation job progress to see completed files, the current file, attached proxies, and any failures.

Instructions

Progress of a create_proxies job: files done, current file, attached proxies, failures.

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": {
      "jobId": "<jobId>"
    },
    "name": "proxy_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
waitSecondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations and no output schema, the description carries the full burden; it does disclose the returned data (files done, current file, attached proxies, failures), which is genuinely useful. However, it never says whether the call blocks, how waitSeconds affects behavior, or whether completed job state persists, leaving the operation's most consequential trait undisclosed.

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

Conciseness4/5

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

A single front-loaded sentence with no filler, and the field list is a compact enumeration. It is efficient, though its terseness is what leaves parameters and job lifecycle unexplained.

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

Completeness2/5

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

For a job-status polling tool with no annotations, no output schema and zero parameter documentation, the description should explain the polling contract and waitSeconds behavior. It conveys none of that.

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

Parameters2/5

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

Schema description coverage is 0% and the description mentions neither of the two parameters. The required jobId's origin (from create_proxies) and especially waitSeconds' blocking semantics — the key behavioral parameter — are completely undocumented.

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

Purpose4/5

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

States a specific verb and resource: progress/status of a create_proxies job, and enumerates the reported fields. It clearly belongs to the proxy job lifecycle alongside create_proxies/manage_proxies, though it doesn't name a sibling explicitly.

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

Usage Guidelines3/5

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

'Progress of a create_proxies job' implies it should be called after starting that job, but there is no explicit when-to-use, no statement about polling vs blocking, and no guidance on what to do once the job finishes or fails.

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