Skip to main content
Glama
Podcast MCP
by calebn

list_exported_transcripts

Lists exported transcript files stored next to podcast audio as JSON, returning format, path, metadata, and edit status so you can verify which transcripts are available and current.

Instructions

List transcript files already exported next to the audio as JSON.

Each entry: format, path, name, mime, language, bytes, modified (UTC), current (false when the transcript was edited since the file was written). Read-only.

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

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does declare 'Read-only' and explains the freshness semantics of the 'current' flag. It says nothing about where 'next to the audio' actually resolves, how errors or missing export directories are reported, or whether the scan recurses, so a mutation-free read tool is characterized but not fully specified.

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?

Two short blocks, front-loaded with the purpose before the entry-field breakdown; every line is readable and nothing is padded. The field enumeration is partly redundant with the existing output schema, which is the only minor waste.

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?

An output schema exists, so return values need not be re-explained, and the read-only nature is stated. The remaining gap is the undocumented optional project_path, which is the only lever an agent has to control what gets listed, making the definition adequate but not complete.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter project_path has 0% schema description coverage and is never mentioned in the description, leaving its meaning and the effect of its null default unexplained. The phrase 'next to the audio' hints that a project context is needed but does not connect that to the parameter the agent must supply or omit.

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 ('List transcript files already exported next to the audio as JSON') and scopes it to on-disk exported files, which separates it from in-project listing tools such as list_edit_decisions_tool. It never names a sibling outright, but the 'already exported' qualifier does the disambiguating work.

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 only implied: an agent can infer this is the tool for checking which exports exist and whether they are stale. There is no explicit when-to-use statement, no mention of what to do instead when nothing has been exported yet, and no note about prerequisites such as the project already being loaded.

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