Skip to main content
Glama

set_blend_mode

Change the blend mode of selected clips in Premiere Pro timelines to control how layers blend and composite visually.

Instructions

Premiere Pro expanded operation: set blend mode.

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?

No annotations are provided, so the description carries the full burden of disclosing side effects, prerequisites, and scope. It discloses none of those: no indication of whether it mutates the selected clip, whether it is reversible, or what happens to the previous blend mode.

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 text is very short, but the 'Premiere Pro expanded operation:' preface is filler and the rest simply repeats the tool name. This is under-specification rather than genuine conciseness, since no meaningful information is front-loaded.

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?

With no annotations, no output schema, and no parameter documentation, this description is grossly inadequate. It omits the target object, the required input, the effect of the operation, and any prerequisites, leaving an agent unable to invoke the tool correctly.

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?

The schema defines zero named properties while allowing additionalProperties, and the description does not explain what arguments to pass. An agent cannot determine whether to supply a blend mode string, target clip identifier, or other values, so the description fails to compensate for the empty schema.

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 merely restates the tool name ('set blend mode') with a generic 'Premiere Pro expanded operation' prefix. It gives no specific object, target, or blend mode values, and does nothing to distinguish this from siblings like set_frame_blend or set_effect_property.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool, what must be selected first, or how it relates to alternative operations. No exclusions or alternative tool mentions are provided, so an agent cannot decide between this and similar clip/appearance setters.

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