Skip to main content
Glama

Save a Reel Studio reel to the library

save_shorts_reel

Deliver one finished reel made with the reel-studio workflow (get_workflow_instructions {workflow:"reel-studio"}): checks the MP4 in the workspace is a playable video, copies it out and saves it as a completed project in the user's VidGuy library and on the Reel Studio page (My reels), where it plays and opens in the editor. Call it once per finished reel, after shorts check render passed. On a timeout, retry once with the same inputs; never re-render to retry. Free.

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": {
      "videoPath": "<videoPath>",
      "title": "<title>",
      "topic": "<topic>",
      "slug": "<slug>"
    },
    "name": "save_shorts_reel"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe reel's slug (lowercase letters, digits, dashes)
titleYesA short title for the library, e.g. the hook line
topicYesThe user's topic or brief as given (the script itself stays in the workspace)
templateNoThe Reel Studio template id used, when one was
videoPathYesWorkspace path of the finished MP4, e.g. ~/work/shorts/<slug>/reel.mp4

Output Schema

NameRequiredDescriptionDefault
videoUrlNo
editorUrlNo
projectIdNo
libraryUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / template / description
      Previous value: -"The Shorts Studio template id used, when one was"New value: +"The Reel Studio template id used, when one was"
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, openWorld=false) the description discloses validation of the MP4, the copy-out, dual persistence to the library and the Reel Studio page, retry-on-timeout semantics, and that the call is free. The one gap is idempotency: idempotentHint=false plus "call it once per finished reel" leaves unclear whether a repeated call with identical inputs creates a duplicate library entry.

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?

The action and prerequisites are front-loaded, and the retry rule is a compact, useful sentence. A few phrases, such as "where it plays and opens in the editor," are decorative rather than decision-relevant.

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?

With annotations, an output schema, and full schema coverage, the description covers preconditions, effects, and failure handling well. The only unresolved point an agent might need is what happens on a repeat invocation with the same inputs, which matters given idempotentHint=false.

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 description coverage is 100%, so all five parameters are already documented, and the description only lightly echoes this by noting the MP4 lives in the workspace and is validated as playable. No additional meaning (formats, slug uniqueness, how topic vs template are used) is added.

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?

Uses a specific verb and resource ("Deliver one finished reel") and scopes it to reels produced by the reel-studio workflow, referencing get_workflow_instructions {workflow:"reel-studio"}. It also states the concrete side effects (copies MP4 out, saves to VidGuy library and My reels), so an agent can tell this apart from generic save/generate siblings.

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 preconditions and cadence: call once per finished reel, only after `shorts check render` passed, and retry once with identical inputs on timeout rather than re-rendering. It stops short of naming a sibling alternative (e.g. save_faceless_video) or a when-not-to-use case, which keeps it from a 5.

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