Skip to main content
Glama

loop_clip

Repeats a video clip 2 to 20 times, extending playback or building looping sequences for AI-generated video projects.

Instructions

Repeats the clip (2-20 times).

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": {
      "video": "<video>"
    },
    "name": "loop_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
timesNo
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds the 2-20 repetition bound, which is genuinely new information not present in the schema. It says nothing about whether a new clip is produced versus the source being modified, or what happens to audio/tracks across repetitions.

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?

One short sentence, front-loaded with the verb and including the range inline. Nothing is wasted, though the terseness borders on under-specification rather than deliberate economy.

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 mutation tool with no output schema and zero schema description coverage, the definition is too thin. An agent still lacks the identifier format for the required 'video' parameter and any statement of the effect on the source clip or resulting output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and largely fails. It clarifies that 'times' means repeat count and bounds it to 2-20, but the required 'video' parameter gets no explanation at all (no id, path, or format guidance), leaving the most important input undocumented.

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?

States a specific verb ('Repeats') and resource ('the clip'), which distinguishes it from siblings like reverse_clip, trim_clip, and change_speed. It stops short of differentiating it from the arguably similar boomerang, but an agent can identify the operation without opening the schema.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as boomerang or extend_clip that also change clip duration/length. Usage is only implied by the verb.

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