Skip to main content
Glama

Keep a clip to use again

save_clip
Idempotent

Keep a finished output of a video (output_id from check_video) as a reusable asset; its asset_id goes in asset_ids of edit_video or create_video. Cost: Free: no credits.

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_id": "<video_id>",
      "output_id": "<output_id>"
    },
    "name": "save_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
video_idYesThe video id from list_videos.
output_idYesThe clip (or hook, or main film) to keep, from check_video, e.g. short-2-9x16.

Output Schema

NameRequiredDescriptionDefault
codeNo
costNo
errorNo
stateNo
statusNo
dry_runNo
messageNo
plan_idNo
style_idNo
video_idNo
availableNo
import_idNo
output_idNo
studio_urlNo
version_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / output_id / pattern
      Removed value: -"^[a-z0-9-]{1,80}$"
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true; the description adds the cost profile (free, no credits) and the asset-handle lifecycle, which the annotations do not convey. It does not describe failure modes such as saving an unfinished output, so it falls short of a 5.

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?

One dense sentence that front-loads the action and result, then appends cost. No redundant restatement of the title or schema.

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

Completeness5/5

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

For a simple two-parameter save tool with full schema coverage, an output schema, and rich annotations, the description supplies the one thing missing from structured data: how this fits into the check_video -> save_clip -> edit_video chain.

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 coverage is already 100%, so the baseline is 3; the description earns extra by explaining what output_id actually is (a clip, hook, or main film, e.g. short-2-9x16) and where it is copied from, which the schema only partially implies.

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?

States a specific verb (keep/save) applied to a specific resource (a finished output of a video), and distinguishes itself from check_video by identifying that tool as the source of output_id rather than the thing being done.

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?

Gives clear workflow context: output_id comes from check_video, and the resulting asset_id is fed into edit_video or create_video. It does not state any when-not-to-use condition or what happens if the same output is saved twice, but the positive routing is explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources