Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Give a film their media

add_studio_video_media

Put files from the film's brand Library — their photos, logo, product shots, footage — on a film as its own media, as the Video tool's "Your media" does. FREE. Get the ids from list_brand_assets, or store a file at a link first with upload_brand_asset. Each file is looked at in the background (what it shows; for a clip, its usable stretches); then the director uses them when it writes or edits the storyboard — say how in studio_video_message ("use the product photo in scene 2, my logo on the end card") — or pin one to a scene with edit_studio_video_storyboard place_media / insert_media_scene using the returned media[].id. Add them BEFORE describing the film when you can, so the first storyboard is written around them. Up to 40 files per film. To make a film FROM their video instead, use create_motion_project from.

Input Schema

NameRequiredDescriptionDefault
asset_idsYesLibrary asset ids (list_brand_assets / upload_brand_asset), in the order to add them
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_idYesProject id from create_motion_project. 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: -"Project id from create_motion_project"New value: +"Project id from create_motion_project. 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.8/5.0
Behavior5/5

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

Annotations are sparse (non-readonly, non-idempotent, non-destructive), and the description adds substantial context: media is processed in the background with content and usable-stretch analysis, the operation is FREE, up to 40 files per film, and files should be added before storyboarding. It also explains the returned media[].id for later pinning, which is not in the schema.

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 description is long but front-loads the core action and cost, then layers workflow guidance in a logical order. Most sentences carry distinct operational value, though a couple of clauses could be tightened without loss.

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?

Given no output schema and minimal annotations, the description covers the critical unknown: what happens after adding (background analysis and usable-stretch detection), how to use the returned ids, file limits, ordering advice, and the sibling alternative. An agent has everything needed to invoke it correctly.

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 100%, so the baseline is 3. The description adds value by explaining that asset_ids come from list_brand_assets/upload_brand_asset and their order matters, and that project_id comes from create_motion_project. It does not mention the optional user_goal parameter, keeping it just shy of a 5.

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 precise verb and resource — putting brand Library files onto a film as its own media — and distinguishes itself from siblings like create_motion_project `from`, edit_studio_video_storyboard, and studio_video_message by naming when each is appropriate. The analogy to the Video tool's "Your media" makes the effect concrete.

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?

Explicitly tells the agent where to get asset ids (list_brand_assets / upload_brand_asset), when to add media (before describing the film), how to direct usage (studio_video_message or edit_studio_video_storyboard place_media/insert_media_scene), and when to use a sibling instead (create_motion_project `from`). No inference needed.

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