Skip to main content
Glama

Sequencer Studio

open_sequencer_workspace
Read-only

Open the Sequencer workspace browser to view projects, recent creations, and shot previews. Read-only. Creation starts only after a user chooses a task and approves its plan and cost.

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": "open_sequencer_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceIdNo
startingTaskNoA skillId returned by list_sequencer_skills, or product-ad, animate-image or short-video.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / startingTask / description
      Added value: +"A skillId returned by list_sequencer_skills, or product-ad, animate-image or short-video."
    • removedInput schema / properties / startingTask / enum
      Removed value: -[
      -  "product-ad",
      -  "animate-image",
      -  "short-video",
      -  "remotion-motion-design",
      -  "film",
      -  "url-to-video",
      -  "create-game",
      -  "restaurant-menu-to-video",
      -  "news-to-video",
      -  "architectural-walkthrough",
      -  "article-to-podcast"
      -]
    • addedInput schema / properties / startingTask / maxLength
      Added value: +100
    • addedInput schema / properties / startingTask / minLength
      Added value: +1
    • addedInput schema / properties / startingTask / pattern
      Added value: +"^[a-z][a-z0-9]*(?:-[a-z0-9]+)*$"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, and the description still adds real behavior: it clarifies that opening the browser performs no creation, and that generation is gated on user task selection plus plan-and-cost approval. It stops short of saying what the tool returns or what happens if startingTask is supplied.

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?

Three short sentences, front-loaded with the purpose and immediately followed by the read-only guarantee. "Read-only" slightly repeats the annotation set, but at this length it is defensible emphasis rather than waste.

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 two-optional-parameter, no-output-schema browser-opening tool, the description covers purpose, safety posture, and the downstream approval gate that governs activation. An agent has enough to call it correctly without knowing the return shape.

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 50%: startingTask is documented in the schema (including its skillId relationship to list_sequencer_skills), while workspaceId carries only a pattern and length constraints. The description adds no parameter-level meaning at all, leaving the workspaceId gap to the schema alone.

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?

States a specific verb and resource ("Open the Sequencer workspace browser") plus the content surfaced (projects, recent creations, shot previews). It is clearly distinct from list_workspaces/get_workspace in kind, but it never names a sibling it replaces or defers to, so differentiation is implicit rather than explicit.

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?

The line "Creation starts only after a user chooses a task and approves its plan and cost" implies this is the entry point before any generative work, which is useful context. However, it never states when to call this versus the many adjacent listing/opening tools (list_sequencer_skills, get_sequencer_capabilities, list_workspaces), so the agent must infer the routing.

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.