Skip to main content
Glama

Transcribe a video

transcribe_video

Transcribes the speech of a video or audio file into text and subtitle files (SRT, VTT, TXT). Uses the user's Klipa credits like on the website.

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

Input Schema

NameRequiredDescriptionDefault
source_idNoInstead of video_url: an upload_id returned by create_upload_link, or the job_id of a finished Klipa job to chain on its result. Empty when video_url is set.
video_urlNoPublic link to a video the user owns or is allowed to edit. Direct file links are not supported (files go through create_upload_link). Empty when source_id is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already establish that this is non-read-only, non-idempotent, open-world, and non-destructive. The description adds useful behavioral context by naming the produced subtitle formats and disclosing that the operation consumes Klipa credits. It does not explain whether the work is asynchronous, how credits are charged on failure, or what job result is returned, which keeps it from a 5.

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 description is two front-loaded sentences with no filler. It states the core action and output formats first, then adds the credit behavior. The phrase "like on the website" is informal but does not create meaningful bloat.

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?

For a two-parameter tool with full schema coverage and annotations, the description covers the core action, output file types, and credit consumption. With no output schema, however, it does not clarify the return shape, job/polling behavior, or how to retrieve results, leaving a clear gap for an agent invoking a non-idempotent operation.

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%, and the schema already explains source_id versus video_url, including their mutual exclusivity and defaults. The description adds no parameter-level meaning beyond that baseline, which is appropriate for a 3 when the schema does the heavy lifting.

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 gives a specific verb and resource: it transcribes speech from a video or audio file into text and subtitle files. It names the output formats SRT, VTT, and TXT. It does not explicitly distinguish this from nearby tools such as add_subtitles or extract_audio, so it falls short of a 5.

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?

The description does not state when to use this tool versus alternatives, nor does it provide exclusions or prerequisites. The implied use case is transcription, but an agent receives no routing guidance between this tool and siblings like add_subtitles, extract_audio, or create_upload_link.

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