Skip to main content
Glama

Export a clip to a folder

export_clip

Copy a finished clip to a destination folder using its final filename. Use it to save a rendered 9:16 clip from Clips Kitty to disk for upload or backup.

Instructions

Copy a finished clip out to a folder, with its final filename.

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>",
      "folder": "<folder>"
    },
    "name": "export_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesDestination folder
clip_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden. It discloses that this copies rather than moves and names the final filename, but it omits whether existing files are overwritten, required permissions, side effects, and error conditions.

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 communicates the action, resource, destination, and resulting filename efficiently.

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 write/export operation with no annotations and no output schema, the description is too sparse. It does not cover whether the folder must exist, overwrite behavior, what happens with an unfinished clip, or what the tool returns.

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 coverage is 50%: folder is described as the destination, while clip_id has no schema description. The description partially compensates by implying clip_id refers to a finished clip and noting the final filename, but it does not explain clip_id format or folder constraints beyond destination.

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: copy a finished clip out to a folder, with its final filename. It is clear what the tool does, but it does not differentiate from sibling publish/upload tools or name an alternative.

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 explicit when-to-use or when-not guidance, and no alternatives are named. 'Finished clip' implies a prerequisite, but the description does not explain when to export versus publish or upload.

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