Skip to main content
Glama
Sign In

Treza

by io.github.treza-labs
OverviewDiscussionsAdmin

Get transcript

get_transcript
Read-onlyIdempotent

Read what is said in a video or audio file the account owns: the full text plus timestamped segments. This is how you know what a clip is about. Call it before writing anything that has to match the footage (a hook, a title, a caption line, a description) and before choosing which seconds to keep: segment times go straight into a trim through edit_asset or edit_project. The first read of a file transcribes it (a few cents, about a minute, waited on inside this call); the same file is free after that. Files up to 25 minutes; for longer, use a clip template. 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": {
      "sourceUrl": "<sourceUrl>"
    },
    "name": "get_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoISO-639-1 hint ("en", "es") when the language is known.
sourceUrlYesThe video or audio url, from list_assets or a run's outputs in get_run.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds behavior the schema cannot: the first read performs a transcription that costs a few cents and takes roughly a minute while blocking inside the call, while repeat reads of the same file are free. It also discloses the required pipelines:run scope and the 25-minute file limit. The one gap is that it doesn't say what happens on an unsupported or private URL, but the operational picture is otherwise strong.

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?

Front-loaded with the core action and return shape, then usage, then cost/latency/limits. Every sentence carries information, though the middle sentence is packed with several clauses at once and could be split for scannability.

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?

Despite no output schema, the description states the return shape (full text plus timestamped segments), plus cost, latency, free-reread behavior, size limit, and required scope. Nothing an agent needs to decide whether and how to call it 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 documented there, including that sourceUrl comes from list_assets or get_run outputs and that language is a 2-letter ISO hint. The description adds no parameter-level detail of its own, so the baseline of 3 applies.

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 ('Read what is said in a video or audio file the account owns') and names the return payload ('full text plus timestamped segments'). It also positions itself relative to siblings by pointing forward to edit_asset and edit_project for the downstream trim.

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?

Gives explicit when-to-use conditions: before writing anything that must match the footage (hook, title, caption, description) and before choosing which seconds to keep. It also names the exclusion and alternative: files over 25 minutes should use a clip template instead.

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