Skip to main content
Glama
Sign In
Adobe Premiere Pro MCP

Adobe Premiere Pro MCP

by compimprove
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

is_work_area_enabled

Check if a work area is enabled in an active Premiere Pro project to determine whether custom in/out range editing is available for timeline operations.

Instructions

Premiere Pro expanded operation: is work area enabled.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

D1.5/5.0
Behavior1/5

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

With no annotations and no description of behavior, the agent is left without any information about side effects, return values, or operational characteristics. The description neither explains what the tool checks nor whether it performs any action, failing to meet the burden when annotations are absent.

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

Conciseness1/5

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

The description is extremely brief, but it is under-specification rather than concise efficiency. A single phrase with no substantive content fails to meet the standard of informative brevity; it is more like a placeholder than a description.

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?

Even for a simple tool with no parameters or output schema, the description must clarify the purpose of checking if 'work area is enabled' and what 'enabled' means. It lacks any contextual information, leaving the tool ambiguous and incomplete.

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?

The tool has zero parameters, and the input schema fully describes the empty contract. According to the rubric baseline, a description need not add parameter details for a no-parameter tool. The description adds no value but does not contradict the schema, so a baseline score is awarded.

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

Purpose1/5

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

The description 'Premiere Pro expanded operation: is work area enabled' simply restates the tool name without explaining what it does, what 'work area' refers to, or what result it provides. It is a tautology, lacking a specific verb or resource outcome, and does not distinguish from sibling tools like get_work_area or set_work_area.

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 context is given for when to use this tool, what it is for, or how it differs from related tools (e.g., get_work_area, set_work_area). There is no mention of prerequisites, conditions, or alternatives, providing zero guidance for tool selection.

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