Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Join a rough cut

join_studio_video_cut
Idempotent

Join a ROUGH CUT — a film made from several of their clips (create_motion_project from.asset_ids; get_studio_video shows rough_cut) — into one film, as the Video tool's Join does. Also PUTS A FINISHED STORYBOARD FILM TOGETHER AGAIN (nothing being made), so a change to its captions or overlays that needs no new scene reaches its file. Free: nothing is generated or charged, the clips are joined as they are, in order, and an unchanged film answers with the file it already has. Answers joined: true with export_url, or joining: true (poll get_studio_video until ready with export.url). A cut is not a film the director edits: to change the joined film (captions, motion graphics, a voice, new scenes), open it as one film with create_motion_project from: { cut_of: <this project_id> } and talk to that film with studio_video_message.

Input Schema

NameRequiredDescriptionDefault
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
project_idYesThe rough cut's project id. The bare project id or the library id ("studio-video:<uuid>" from list_creations / find_creation) both work.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. Changed3 schema fields changed
    • changedInput schema / properties / project_id / description
      Previous value: -"The rough cut's project id"New value: +"The rough cut's project id. The bare project id or the library id (\"studio-video:<uuid>\" from list_creations / find_creation) both work."
    • removedInput schema / properties / project_id / format
      Removed value: -"uuid"
    • addedInput schema / properties / project_id / pattern
      Added value: +"^(?:studio-video:)?[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations, it says the operation is free, generates nothing new, joins clips as-is in order, and returns the existing file when unchanged. It also discloses return states: joined: true with export_url, or joining: true requiring polling get_studio_video until ready with export.url.

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 main purpose is front-loaded, and each sentence covers a distinct need: rough-cut definition, storyboard use case, cost behavior, return states, and the editing alternative. The long paragraph and all-caps parentheticals make it denser than ideal, but little is wasted.

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 mutation tool with no output schema, the description covers the key operational details: cost, ordering, idempotent behavior, async polling, and the correct alternative for editing. An agent has enough information to call it correctly and interpret the result.

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 project_id and user_goal are already documented in the schema. The description adds contextual references to the rough cut project and create_motion_project from.asset_ids, but no additional parameter syntax or constraints beyond the schema.

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 first sentence gives a specific verb and resource: joining a rough cut into one film, and it also covers the storyboard-film case. It distinguishes this tool from creation/editing siblings by naming create_motion_project and studio_video_message as the way to edit the film afterward.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool: joining a rough cut, and re-joining a finished storyboard film after caption or overlay changes that need no new scene. It also states when not to use it: to change the joined film, open it as a film with create_motion_project and use studio_video_message.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources