Klipa

Resize a video

resize_video

Changes the aspect ratio and/or resolution of a video, fitting (with bars), filling (cropping) or stretching.

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

Input Schema

Name	Required	Description	Default
`mode`	No	fit = keep everything with bars; fill = crop to fill; stretch = distort	fit
`ratio`	No	Target aspect ratio	original
`source_id`	No	Instead 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_url`	No	Public 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.
`resolution`	No	Output resolution	720p

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The annotations already declare that this is a non-read-only, open-world, non-idempotent, non-destructive operation, so the safety profile is covered. The description adds useful meaning about fit/fill/stretch behavior, but it does not disclose output/job behavior, credit implications, or processing constraints.

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?

The description is a single front-loaded sentence with no wasted wording. It states the operation and concisely explains the three modes.

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

Completeness3/5

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

The tool has a fully documented five-parameter schema and annotations covering safety, but no output schema. The description does not explain what the tool returns or how job chaining works, which leaves a meaningful gap for a media-transformation operation.

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 schema already documents all five parameters, including enum meanings. The description restates the mode semantics already present in the schema and adds no new syntax or constraints, so the baseline of 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 and resource: it changes a video's aspect ratio and/or resolution, and it names the three transformation behaviors. It does not explicitly distinguish this from nearby capabilities such as reframe_video or convert_video, so sibling differentiation is left implicit.

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?

The description says what the tool does but gives no guidance on when to use it instead of alternatives. It does not mention reframe_video, convert_video, rotate_video, or any other sibling, nor does it state prerequisites or exclusions.

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

All Klipa tools Inspect

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

Need Help?