Skip to main content
Glama
Sign In

Treza

by io.github.treza-labs
OverviewDiscussionsAdmin

Render timeline project

render_project

Render a timeline project to a finished video, exactly as the editor's Export does. Costs a few cents a minute of video in credits (no generation, just the cut). Renders in the background and returns a jobId: poll get_project_render until it finishes; the file also lands in list_assets. Call it once per edit. Needs the pipelines:run 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": {
      "projectId": "<projectId>"
    },
    "name": "render_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYesFrom list_projects or open_run_in_timeline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the supplied annotations, the description discloses cost behavior (credits per minute), asynchronous background execution with a returned jobId, the polling requirement, the artifact destination, and the necessary OAuth scope. These are exactly the operational details an agent needs for a non-read-only render operation.

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 front-loaded with the core action, then moves through cost, async behavior, polling, output destination, call frequency, and scope. Every sentence carries distinct operational value with no redundant wording.

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 one-parameter asynchronous render tool with no output schema, the description covers cost, execution model, completion tracking, output location, scope requirements, and usage frequency. Nothing essential for correct invocation appears to be 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?

There is only one parameter, projectId, and schema description coverage is 100%, including the note that it comes from list_projects or open_run_in_timeline. The description does not add further meaning beyond the schema, so the baseline of 3 is appropriate.

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 description states a specific verb and resource (render a timeline project to a finished video) and explicitly distinguishes this operation from generative siblings with 'no generation, just the cut.' It also equates the behavior to the editor's Export, so an agent knows precisely what result to expect.

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 usage constraint ('Call it once per edit'), names the follow-up tool for completion ('poll get_project_render'), and states where the resulting file appears ('list_assets'). The required 'pipelines:run' scope is also called out, leaving little ambiguity about when and how to use it.

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