Skip to main content
Glama

set_frame_blend

Enable or disable frame blending on selected clips in Adobe Premiere Pro to control motion smoothing.

Instructions

Premiere Pro expanded operation: set frame blend.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

D1.7/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 tool's side effects are completely opaque. The description does not say whether it modifies selected clips, changes duration/rendering, requires specific sequence settings, or affects other properties. The agent has no safety or expectation information.

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 short but under-specified rather than helpfully concise. 'Premiere Pro expanded operation' is filler that does not inform the agent, and the core phrase merely repeats the tool name.

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?

The tool has no annotations, no output schema, no declared parameters, and a one-line tautological description. In the context of a large sibling set with many clip/sequence operations, there is insufficient information for an agent to call this tool safely or correctly.

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?

The schema declares zero parameters (though additionalProperties is true), and the rubric gives a baseline of 4 for zero-parameter tools. However, the description provides no hint about whether this tool accepts optional parameters or how the frame blend setting is specified, so it fails to add the clarity that the loose schema demands.

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 'Premiere Pro expanded operation: set frame blend' essentially restates the tool name and adds only the vague category 'expanded operation'. It does not explain what frame blend is, what it does to media, or how it differs from related operations like set_time_interpolation or set_clip_speed_qe.

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?

There is no guidance on when this tool should be used, which clips it applies to, or what alternatives exist. Given siblings like set_time_interpolation that can control interpolation methods and set_blend_mode for compositing, an agent cannot determine when set_frame_blend is the correct choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tro2789/scout-premiere-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server