Skip to main content
Glama

transcribe

Generate AI transcripts for selected clips or an entire bin to enable text-based editing; optionally clear existing transcripts.

Instructions

Run Resolve's AI audio transcription on clips (or a whole bin) — needed for transcript and text-based editing. clear=true removes existing transcriptions instead. Can take a while for long media.

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

Input Schema

NameRequiredDescriptionDefault
binNo
clearNo
itemsNo
speaker_detectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does well to disclose that the operation is long-running ('Can take a while for long media') and that `clear=true` destroys existing transcriptions rather than creating them. It says nothing about whether existing transcripts are overwritten, whether the call blocks, or what state the media is left in on failure.

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?

Three tight sentences: primary action and scope first, the routing/dependency hint second, the destructive `clear` behavior and runtime caveat last. Nothing is padded or restated from the schema.

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 four-parameter, zero-annotation, no-output-schema mutation tool, the definition covers purpose, scope, runtime and the destructive mode, which is a decent baseline. It still leaves `speaker_detection` undocumented and gives no sense of what the result looks like or how to confirm transcription completed.

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 0%, so the description must compensate. It explains `bin` (whole bin instead of clips), `clear` (removes existing transcriptions), and implies `items` (clips), but `speaker_detection` is never mentioned, leaving one of four parameters with no meaning anywhere.

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?

Specific verb and resource: 'Run Resolve's AI audio transcription on clips (or a whole bin)', and it names the downstream dependency `transcript` plus text-based editing. It is clearly distinguishable from the sibling `transcript` reader, though it never explicitly says how it differs.

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

Usage Guidelines4/5

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

States the trigger condition — it is 'needed for `transcript` and text-based editing' — and explains the alternative mode when `clear=true`. No explicit when-not-to-use case (e.g., media already transcribed) is given, so it stops short of a full routing guide.

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