Skip to main content
Glama

transcript_export

Export a video transcript as txt, srt, vtt, or json, optionally filtered to one speaker, and return it as text or save it to a file.

Instructions

Export the transcript to a formatted string or file in txt, srt, vtt, or json format, optionally filtered to a single speaker.

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

Input Schema

NameRequiredDescriptionDefault
fileNoOptional path to a video or subtitle file; defaults to the playing file
formatNoOutput format (default txt)
outputNoOptional output file path. Omit to receive the formatted text in the response.
speakerNoOptional speaker filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden; it does explain that output can go to a file or be returned inline and that filtering is optional. However, it says nothing about overwrite behavior for an existing output path, filesystem permissions, or what happens when no transcript exists, which matters for a tool that writes files.

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?

A single front-loaded sentence that states the action, the resource, the output variants, and the filter with no filler. Nothing in it is redundant framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter, all-optional tool with full schema coverage and no output schema, the description covers the operation, formats, and destinations adequately. Only error and overwrite behavior are unaddressed, which is a minor gap at this complexity level.

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%, so each of the four parameters is already documented, including the format enum and the file-vs-response distinction. The description restates the format list and speaker filter but adds no syntax, default, or path-resolution detail beyond the schema.

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?

The description names a specific verb and resource (export the transcript) plus the four supported formats and the optional speaker filter, so the operation is unambiguous. It does not distinguish itself from siblings such as transcript_get or transcript_summary, which is the only thing keeping it from a 5.

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

Usage Guidelines3/5

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

Usage is implied by the destination wording ('formatted string or file') and the speaker filter, but there is no explicit statement of when to choose this over transcript_get or transcript_summary, nor any prerequisite or exclusion guidance.

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

Deploy Server

Other Tools