Skip to main content
Glama
Sign In
MoviePy MCP Server

MoviePy MCP Server

by vive1101011
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

loop_clip

Repeat a video or audio clip by specifying either the number of repetitions or the total desired duration.

Instructions

Repeat a clip. Give either n_times OR total_duration_seconds.

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

Input Schema

NameRequiredDescriptionDefault
clip_idYes
n_timesNo
total_duration_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without covering side effects (e.g., whether the original clip is modified), what happens if both parameters are provided, or return behavior. This is a significant gap.

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 concise sentence, front-loaded with the main action ('Repeat a clip') followed by a useful parameter hint. Every word earns its place with no redundancy.

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?

The description lacks important behavioral details such as validation rules, edge cases, and side effects. With no annotations and no parameter descriptions, it is insufficient for complete understanding, even though an output schema may exist to explain return values.

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 schema has no descriptions (0% coverage), so the description adds value by clarifying the mutual exclusivity of n_times and total_duration_seconds, hinting that one should be provided. It does not explain units or exact effects, but the names are self-explanatory.

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 repeats a clip, using a specific verb 'Repeat' and resource 'clip'. It distinguishes this from sibling tools like trim or change_speed by focusing on repetition as the core function.

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

Usage Guidelines3/5

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

The description provides parameter guidance ('Give either n_times OR total_duration_seconds') but no explicit when-to-use vs alternatives or exclusions. The usage is implied from the purpose, making it adequate but not explicit.

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

Deploy Server

Other Tools