Skip to main content
Glama

OpenClip

by app.openclip
OverviewDiscussionsAdmin

Edit Video Tool

edit_video

Edit an already-uploaded file (a video hashid from create_upload or list_videos) with one operation: crop, trim, rotate, resize, compress, or mute. This is FREE and only needs an account, no subscription.

To use a local file: call create_upload, PUT the bytes to the returned upload_url, then pass that video id here as file. Do NOT call complete_upload (that starts the paid clip pipeline); this free tool reads the uploaded file directly.

Operation params:

  • crop: aspect ("1:1"|"9:16"|"16:9"|"4:5") OR x,y,width,height (ints).

  • trim: start_ms and end_ms (ints, required).

  • rotate: degrees (90|180|270) and/or flip (none|horizontal|vertical).

  • resize: width and height (ints).

  • compress: target_mb (number) OR crf (int 18-32).

  • mute: no extra params.

Processing is ASYNCHRONOUS: this returns a tool_job hashid and status: "queued". Poll get_tool_job_status with that tool_job until it reports completed, then it returns the downloadable output URL. Free usage is rate-limited per day with per-file size and duration caps; a clear error explains how to lift a limit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
xNocrop: left offset in pixels.
yNocrop: top offset in pixels.
crfNocompress: constant rate factor 18-32 (lower = higher quality).
fileYesThe uploaded video id (hashid) from create_upload (no complete_upload needed) or list_videos.
flipNorotate: none, horizontal or vertical.
widthNocrop/resize: width in pixels.
aspectNocrop: target aspect "1:1", "9:16", "16:9" or "4:5". Use this OR x/y/width/height.
end_msNotrim: end time in milliseconds.
heightNocrop/resize: height in pixels.
degreesNorotate: 90, 180 or 270.
start_msNotrim: start time in milliseconds.
operationYesOne of: crop, trim, rotate, resize, compress, mute.
target_mbNocompress: target output size in megabytes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations are empty, so description carries full burden. It discloses that processing is asynchronous, returns tool_job and status 'queued', and requires polling get_tool_job_status until completed. Also mentions rate limits and size/duration caps, and explains how to lift limits. This is more than minimal behavioral context.

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

Conciseness5/5

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

Well-structured: starts with core purpose and workflow, then an 'Operation params' section that readability is high. Every sentence serves a purpose; no redundant content. The async behavior is front-loaded near the end but clearly marked.

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

Completeness5/5

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

Covers all necessary aspects: input file origin, operation options, async status, polling mechanism, and limitations. The output schema is absent so the return format is described. For a complex multi-operation tool, nothing critical is missing.

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?

Schema coverage is 100%, but the description adds significant meaning by grouping parameters with their operations and clarifying alternatives (e.g., aspect OR x/y/width/height; target_mb OR crf). This goes beyond the schema's per-parameter descriptions. Slight deduction because it doesn't define allowed values for x, y, width, height beyond integers, but schema already lists them.

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

Purpose5/5

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

States a specific verb and resource: edit an already-uploaded video. It lists the six operations (crop, trim, rotate, resize, compress, mute) and clearly distinguishes it from complete_upload. This creates a unique identity among siblings.

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

Usage Guidelines5/5

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

Explicitly explains when to use this tool (free edits on uploaded files) and when not: do NOT call complete_upload for the paid pipeline. Gives clear steps: create_upload, PUT bytes, pass the id here. Provides per-operation guidance in detail.

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

All OpenClip toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources