Skip to main content
Glama

PodLearn

by io.github.blutrich

transcribe_feed

Bulk/season transcription — kick off transcription for up to max (cap 25) not-yet-transcribed episodes of a podcast feed in ONE call. Pass the feed_id from search_podcasts / list_feed_episodes. Already-transcribed episodes are skipped free. COSTS 1 credit per newly enqueued episode (or subscription quota) — CONFIRM the cost with the user first. Enqueue-and-poll: returns each enqueued episode_id; poll get_episode_details until transcription_status is "completed".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNoMax episodes to enqueue (default 10, cap 25)
sinceNoOptional unix-seconds; only episodes published AFTER
beforeNoOptional unix-seconds; only episodes published BEFORE (page back)
feed_idYesPodcastIndex feed id (from a search_podcasts / list_feed_episodes result)

TDQS

A4.9/5.0
Behavior5/5

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

Discloses mutation (enqueue), cost (1 credit per episode), skip of already-transcribed episodes, return type (episode_ids), polling requirement. Annotations (readOnlyHint=false, destructiveHint=false) are consistent and description adds significant behavioral context.

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?

Two well-structured sentences, front-loaded with purpose, no redundant information. Every sentence adds value.

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?

Despite no output schema, description covers what is returned (episode_ids) and how to use them (poll). Includes prerequisites, cost, and behavior. Complete for a tool with 4 parameters.

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 covers 100% with descriptions. Description adds practical context: default max (10), cap (25), purpose of since/before (publish date filtering), and source of feed_id. More than baseline 3 due to added usage nuance.

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?

Description clearly states it bulk-transcribes podcast episodes, specifies source (feed), and distinguishes from related tools like start_transcription (single episode) and transcribe_url (URL-based). Verb+resource+scope are specific.

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?

Provides when to use (bulk feed transcription), prerequisites (feed_id from search/list tools), cost advice (confirm with user), and post-invocation steps (poll get_episode_details). Explicitly distinguishes from alternatives.

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

All PodLearn toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation4/5

Tools are largely distinct, covering separate actions (search, get, list, generate, transcribe, save). The main potential confusion is between list_episodes and list_feed_episodes, but descriptions clearly separate local from external.

Naming Consistency5/5

All tools follow consistent verb_noun snake_case patterns (get_, list_, search_, generate_, transcribe_, save/remove), with no mixed conventions or unexpected styles.

Tool Count3/5

25 tools is at the high end for a server of this scope. The broad domain justifies many functions, but the count feels heavy and some tools could be consolidated without losing clarity.

Completeness4/5

Discovery, ingestion, transcription, lesson generation, and user account management are all well covered. Minor gaps exist, such as no way to delete or update lessons beyond save/remove.

Resources