Skip to main content
Glama
Sign In

Treza

by io.github.treza-labs
OverviewDiscussionsAdmin

Open run in timeline

open_run_in_timeline

Turn a finished run (run_pipeline, assemble_video or edit_asset) into an editable timeline project and return its projectId: each shot, the narration, the music and the captions land on their own tracks. This is the step that creates a project. When the person asks to change a finished video and list_projects does not show it, call this with the pipelineId that made it rather than rendering it again from scratch. Each call opens a fresh copy. Needs the pipelines:write scope.

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": {
      "pipelineId": "<pipelineId>"
    },
    "name": "open_run_in_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
runIdNoA specific run. Omit for the newest finished run that made a cut.
pipelineIdYesThe pipeline that made the video (assemble_video and edit_asset return it).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations: it discloses a required OAuth scope (pipelines:write), that each call creates a fresh copy (consistent with idempotentHint=false), and that it is the step that creates the project. That materially reduces the risk of an agent misjudging the side effects of a non-readOnly, non-idempotent call.

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 leads with the effect and the return value, then gives the trigger and the scope. Every sentence carries information, though 'This is the step that creates a project' partly restates the opening clause and could be folded in.

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-parameter mutation with no output schema, the description covers the return value (projectId), the auth requirement, the copy-per-call behavior, and the situation that should trigger a call. Nothing needed to invoke it correctly is missing.

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 coverage is 100%, and both parameters are already documented in the schema. The description only restates that the pipelineId should be the one that made the video, which the schema already says, and it says nothing extra about runId selection such as the newest finished run with a cut.

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 specific verb and resource: it turns a finished run from named source tools (run_pipeline, assemble_video, edit_asset) into an editable timeline project and returns a projectId. The added detail that shots, narration, music and captions land on separate tracks separates it from create_editor_project and render_project, which is what an agent needs to choose correctly.

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 gives an explicit trigger ('when the person asks to change a finished video and list_projects does not show it') and an explicit alternative to avoid ('call this ... rather than rendering it again from scratch'). It also names the fallback diagnostic (list_projects) and the correct input source (the pipelineId that made the video).

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

All Treza 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