Skip to main content
Glama

job_transcribe_premium

Transcribe an audio or video file (Whisper large-v3-turbo)

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": {
      "media_url": "<media_url>"
    },
    "name": "job_transcribe_premium"
  }
}

Input Schema

NameRequiredDescriptionDefault
media_urlYespattern https://\S{4,2000}
max_resultsNodefault 10, at most 120

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and does not meet it. It says nothing about cost or rate implications of a "premium" model, whether the call is synchronous or returns a job handle, expected latency for long media, or what happens on unsupported input.

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?

A single front-loaded sentence with no padding; the resource and model are stated immediately. It is efficient, though the terseness leaves the description under-informative rather than tight-but-complete.

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

Completeness2/5

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

There is no output schema and no annotations, so the description should explain what a caller gets back (transcript text, job id, segments, language detection) and any operational constraints. For a transcription job that may be long-running and premium-priced, this is a significant gap.

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 description coverage is 100%, so both parameters are already documented in the schema, giving a baseline of 3. The description adds one piece of meaning beyond the schema: media_url accepts video as well as audio, which the schema's bare string type does not convey.

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?

"Transcribe an audio or video file" gives a specific verb and resource, and the parenthetical names the underlying model (Whisper large-v3-turbo). It stops short of distinguishing this from the sibling job_transcribe, so an agent cannot tell from the text what makes this one "premium".

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says when to pick this over job_transcribe or job_youtube_transcript, and no prerequisites (URL accessibility, file size, supported formats) are stated. The only inferred signal is the "premium" label, which is not explained.

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