Skip to main content
Glama

transcribe

Convert an asset's speech to text on-device with Whisper, saving the result in the OpenScreen project for captions, text lookup, and word edits.

Instructions

Transcribe one asset's speech with OpenScreen's on-device Whisper, as the editor does when it opens a project, and store the transcript in the project: getTranscript, getTranscriptWords, setWordText, removeWords and the captions all read it. A take from stopRecording has none until this runs. Without language, an asset that already has a transcript keeps it, and a transcription the editor is already running is waited for rather than run twice; with language, the asset is transcribed again in it (a run of the editor already in that language is waited for instead), and the word corrections that still match are carried over. The project's vocabulary (setVocabulary) primes Whisper. It runs on this computer and can take minutes on a long recording, more the first time, when the speech model downloads. Media with no audio fails with failure.kind no-audio, which the asset then remembers (assets[].transcriptionFailure in getCurrentDocument). The result gives the language and the word count; it needs no checkpoint, and restoreCheckpoint keeps a transcript made after its checkpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assetIdNoThe asset to transcribe, from getCurrentDocument. Default: the primary asset.
languageNoTranscribe again in this language (ISO 639-1, such as "en" or "fr"), or "auto" to let Whisper detect it. Omit it to keep a transcript the asset already has.
projectIdNoThe project to act on, from listProjects. Omit it only for the project open in the OpenScreen editor, which works only while the app runs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the mutability profile; the description adds substantial beyond-schema behavior: on-device execution, minutes-long latency, first-run model download, no-audio failure with failure.kind `no-audio` persisted to assets[].transcriptionFailure, vocabulary priming, and checkpoint interaction. That is exactly the context annotations cannot carry.

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?

Dense and front-loaded with purpose and consumers first, then language semantics, then runtime/failure caveats. Some sentences are long and closely packed (latency, failure, checkpoint all in one block), which slightly hurts scannability but nothing is wasted.

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?

Complete for a mutation tool with no output schema: covers what it writes, who reads it, which parameters trigger which behavior, runtime cost, model download, failure mode persistence, and checkpoint interaction. An agent has everything needed to call it correctly.

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 the schema already explains assetId, language pattern/enum semantics, and projectId. The description reinforces the language behavior (skip/wait vs re-transcribe) but adds no syntax or format detail beyond the schema. Baseline 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?

States a specific verb (transcribe) and resource (one asset's speech) and ties it to the exact downstream consumers (getTranscript, getTranscriptWords, setWordText, removeWords, captions), which clearly distinguishes it from those siblings.

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 conditional semantics: omit `language` to keep an existing transcript or wait on an in-flight run; supply `language` to re-transcribe and carry over matching word corrections. Also notes a take from stopRecording has none until this runs, so an agent knows exactly when to reach for it.

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