Skip to main content
Glama

set_clip_rotation

Rotate video clips in Adobe Premiere Pro directly through AI commands. Set exact rotation degrees to fix orientation or add creative angles.

Instructions

Premiere Pro expanded operation: set clip rotation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool sets clip rotation, without revealing side effects, required permissions, units, coordinate systems, or whether it affects selected clips.

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 concise in length but the only sentence is boilerplate ('Premiere Pro expanded operation') followed by a tautology. It does not earn its place and is not front-loaded with useful 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?

The description is highly inadequate for a tool with no annotations, no output schema, and only a generic empty input schema. It fails to explain what 'rotation' means, how the value is determined, or what happens when invoked, making it impossible for an agent to use correctly without external knowledge.

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 zero parameters (schema coverage 100% vacuously), so there are no parameter details to document. Per rubric, a tool with 0 parameters gets a baseline of 4, though the description adds no additional context about how rotation is specified (e.g., via selection or default angle).

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 clip rotation' is essentially a restatement of the tool name with spaces. It identifies the verb and resource but provides no additional scope or differentiation from sibling tools like set_clip_scale or set_clip_position.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention any prerequisites, selection requirements, or exclusions, and does not reference sibling tools.

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

Install Server

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/hetpatel-11/Adobe_Premiere_Pro_MCP'

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