MoviePy MCP Server

Overview Schema Source Related Servers Discussions Admin

resize

Adjust video or image dimensions by setting scale, width, height, or both. Provide one dimension to automatically preserve the aspect ratio.

Instructions

Resize a video/image clip.

Give exactly one of: scale (e.g. 0.5), width, height, or width+height. A single dimension preserves aspect ratio.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "clip_id": "<clip_id>"
    },
    "name": "resize"
  }
}

Input Schema

Name	Required	Description	Default
`scale`	No
`width`	No
`height`	No
`clip_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 1, 2026

TDQS

A4.2/5.0

Behavior3/5

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

With no annotations, the description must disclose behavioral traits. It mentions that a single dimension preserves aspect ratio and imposes exclusivity among parameters, but it does not state what happens if none or multiple are provided, nor whether the operation is destructive or returns a new clip. This is adequate but not thorough.

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 two short sentences, front-loaded with the purpose and followed by precise usage constraints. Every sentence earns its place with no redundancy.

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

Completeness4/5

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

Given the simplicity of a resize operation and the existence of an output schema, the description covers the essential usage scenarios. It lacks info on error behavior or whether the clip is modified in place, but for a resize tool, the provided guidance is largely sufficient.

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 description coverage is 0%, so the description carries the burden of explaining parameters. It clarifies the meaning of 'scale' with an example, the notion of 'width' and 'height' as dimensions, and the combination 'width+height'. This adds value beyond the bare schema, though 'clip_id' remains implied.

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?

The description clearly states the tool resizes a video/image clip, using the specific verb 'Resize' and a clear resource. It also differentiates from sibling tools like crop, rotate, and mirror by focusing on resizing dimensions/scale.

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

Usage Guidelines4/5

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

Provides explicit guidance on how to specify dimensions: 'Give exactly one of: scale, width, height, or width+height' and explains that a single dimension preserves aspect ratio. However, it does not explicitly mention when to use this tool over alternatives, though the context is clear enough.

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