Skip to main content
Glama

set_color_value

Set precise color values for Adobe Premiere Pro timeline items. Apply RGB or hex codes to adjust clip colors, labels, or effects directly from the timeline.

Instructions

Premiere Pro expanded operation: set color value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Install Server

TDQS

C2/5.0
Behavior1/5

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

Annotations are absent, so the description bears full responsibility for behavioral disclosure. It only restates that an operation sets a color value, with no mention of side effects, target scope, prerequisites, or reversibility. This is insufficient for a mutating tool.

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 not genuinely concise; it is under-specified. 'Premiere Pro expanded operation' is filler, and 'set color value' just repeats the tool name without adding structured, decision-relevant information.

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?

For a tool with a vague name and no annotations, no output schema, and no parameter documentation, this description is critically incomplete. An agent cannot determine what object it operates on, what inputs it accepts, or how it differs from several similarly named sibling tools.

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 input schema declares no parameters and parameter count is 0, so the baseline is 4. The description adds no parameter detail, but there are no formal parameters for it to explain; additionalProperties true is the only hint of flexibility, and the description does not contradict it.

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 color value' is essentially a tautology of the tool name, with the meaningless boilerplate 'expanded operation' and no object or target. It does not identify what color value is being set or on what resource, and it does not distinguish this from siblings like set_color_label or color_correct.

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?

No guidance is provided for when to use this tool versus alternatives such as set_color_label, color_correct, or set_effect_property. The description gives no context, exclusions, or conditions.

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