Skip to main content
Glama

Transcribe audio

transcribe_audio
Read-only

Speech to caption segments with word timings, using Whisper (via Vercel AI Gateway). 5 credits per started minute. Audio or video file, public https URL, up to 25 MB.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_url": "<audio_url>"
    },
    "name": "transcribe_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
offsetNoShift timings onto the output timeline, e.g. the music track's start
audio_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real behavioral context: the cost model (5 credits per started minute), the provider, and a hard 25 MB input ceiling. What remains undisclosed is the execution model — whether the call returns segments synchronously or must be polled via check_jobs — which matters for a paid, open-world operation.

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 compact sentences carry the output shape, engine, pricing, and input limits with no filler. The core capability is front-loaded, and each clause adds 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?

With no output schema, the description does the right thing by characterizing the return value as caption segments with word timings. For a paid transcription tool the remaining gap is operational — synchronous versus job-based execution and failure behavior on oversized or unreachable URLs — but the essential call contract is complete.

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 coverage is only 50%: audio_url carries a pattern but no description, and offset is documented in the schema only. The description compensates for audio_url's gap by adding accepted media types, the public-https requirement, and the size limit, going meaningfully beyond the structured fields.

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?

"Speech to caption segments with word timings" names the transformation and its output shape precisely, and "using Whisper (via Vercel AI Gateway)" identifies the engine. It does not explicitly distinguish itself from nearby transcript tools such as get_transcript or edit_transcript, but the create-style framing is unambiguous on its own.

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 rather than stated: the agent learns what inputs are acceptable (audio or video, public https URL, 25 MB cap) but gets no explicit when-to-use versus when-not, and no routing to get_transcript for retrieval of an existing transcript. The input constraints do usefully prevent invalid calls, which lifts it above a pure 2.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources