Skip to main content
Glama
Podcast MCP
by calebn

export_transcript

Exports an edited podcast episode’s transcript beside its audio in txt, md, srt, or vtt, reflecting the edited timeline and omitting cut material; preview with a dry run.

Instructions

Write the edited episode's transcript next to the audio; return JSON.

formats: any of "txt", "md", "readable.txt", "srt", "vtt" (default ["md", "srt"]). Files go to the project's export folder under the episode name, all written together or none, and reflect the edited timeline (cut material omitted). dry_run writes nothing and returns the preview only; with_text adds the full reading text. Result keys: language, turns, duration_sec, preview, cue_sample, files (format, path, name, bytes, language, written, current), text. Errors: export_busy (another export is running), transcript_empty.

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

Input Schema

NameRequiredDescriptionDefault
dry_runNo
formatsNo
with_textNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.4
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": false,
      +  "title": "Dry Run",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / formats
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Formats"
      +}
    • addedInput schema / properties / with_text
      Added value: +{
      +  "default": false,
      +  "title": "With Text",
      +  "type": "boolean"
      +}
  2. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
      -  "project_path"
      -]
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses atomic all-or-none writes, the destination folder layout, that cut material is omitted, that dry_run writes nothing, and the export_busy and transcript_empty failure modes. Gaps remain around permissions and whether existing files at the target path are overwritten.

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 purpose leads in one sentence, then formats, destination semantics, dry_run, and error codes follow in a tight block with no filler. Every clause carries operational information an agent would otherwise have to guess.

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 export tool with an output schema and no annotations, this covers dry-run semantics, atomicity, timeline correctness, and error cases well. Listing the result keys is mildly redundant given the output schema, and the undocumented project_path is the remaining hole.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, and it does for three of four parameters: it enumerates the exact format strings with the default ['md','srt'], explains dry_run as preview-only, and explains with_text as adding full reading text. The only omission is project_path, which is never described and whose null default is left unexplained.

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?

States a specific verb and resource plus scope: 'Write the edited episode's transcript next to the audio; return JSON.' That is clearly distinct from sibling export tools by naming the artifact (transcript) and the output formats. It stops short of explicitly naming the sibling it is not (export_audio_tool, export_social_clips_tool), so it lands at 4 rather than 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 through the format list, the dry_run preview mode, and the note that output reflects the edited timeline. There is no explicit when-to-use/when-not statement and no named alternative for audio or clips export, so the agent must infer routing from the artifact name alone.

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