Skip to main content
Glama

Rotate or flip a video

rotate_video

Rotates a video by 90, 180 or 270 degrees and/or mirrors it.

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

Input Schema

NameRequiredDescriptionDefault
flipNoMirror the video horizontally
angleNoClockwise rotation
source_idNoInstead of video_url: an upload_id returned by create_upload_link, or the job_id of a finished Klipa job to chain on its result. Empty when video_url is set.
video_urlNoPublic link to a video the user owns or is allowed to edit. Direct file links are not supported (files go through create_upload_link). Empty when source_id is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. However, the description adds nothing beyond them: it does not say the call creates an asynchronous job, whether credits are consumed, how the source is resolved, or what happens to the original video. For a mutation tool with an open-world hint, that leaves real behavioral gaps.

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

Conciseness4/5

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

A single tight sentence, front-loaded with the verb and the operation's full range; nothing is wasted. It is arguably too terse rather than too long, but structurally clean.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a video-mutation tool with four parameters, no output schema and no annotations covering return values, the description says nothing about the result (job id), required input sourcing, or cost. An agent would know how to rotate but not what to expect back or how to chain the result.

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?

Schema description coverage is 100%, so the flip, angle, source_id and video_url semantics are fully documented in structured data. The description restates the angle set and mirroring but adds no syntax, default value (angle defaults to 90) or interaction rules between source_id and video_url, so baseline 3 applies.

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

Purpose4/5

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

The description states a specific verb (rotates) and resource (a video) plus the concrete parameter space (90/180/270 degrees and/or mirroring), which is more informative than the title repeat. It does not distinguish the tool from the sibling reframe_video, which likely overlaps conceptually, so an agent still has to guess which to pick.

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 explicit when-to-use or when-not-to-use guidance, and no alternative named. The description does not say whether to use this instead of reframe_video, nor that a source (video_url or source_id) must be chosen, which is the main decision an agent faces here.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources