Skip to main content
Glama

video_studio

Open an interactive browser studio to preview, edit, and refine video scenes with a timeline, per-scene controls, and a prompt box for typed edits.

Instructions

Open the studio in the browser: live preview, timeline, per-scene controls and a prompt box where the user can type edits.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "video_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault
openNoopen the browser (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the key side effect of opening the studio in the browser and lists the visible UI features, but it omits permissions, whether the call blocks, what happens after launch, and how the prompt box lifecycle works.

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 a useful colon list of UI elements. Every phrase contributes context, and there is no redundant wording.

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

Completeness3/5

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

For a simple one-parameter UI-launch tool whose schema already documents the parameter, the description explains enough about what opens. It still leaves gaps around when to choose this over related editing tools and what happens after the studio opens, especially since there are no annotations or output schema.

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%, and the single 'open' parameter already documents that the browser opens by default. The prose adds no additional meaning about what setting open to false does or how the parameter interacts with the browser UI.

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 uses a specific verb and resource: it opens the studio in the browser and lists what appears there. It is clear what the tool does, though it does not explicitly distinguish itself from editing-oriented siblings such as video_edit or video_timeline.

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

Usage Guidelines3/5

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

Usage is implied by the mention of a prompt box where the user can type edits, suggesting an interactive manual-editing context. However, the description gives no explicit when-to-use or when-not-to-use guidance and does not route the agent toward or away from sibling tools.

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