Skip to main content
Glama
elibarnett

kie-mcp

by elibarnett
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

speech_to_text

Transcribe audio to text using ElevenLabs Scribe v1. Supports diarization and audio event tagging. Returns transcription text.

Instructions

Transcribe audio to text using ElevenLabs Scribe v1. Supports diarization and audio event tagging. Returns transcription text.

Input Schema

NameRequiredDescriptionDefault
diarizeNoIdentify different speakers
audio_urlYesAudio URL to transcribe
max_creditsNoRefuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.
estimate_onlyNoReturn the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).
language_codeNoLanguage code (e.g. "en", "es"). Auto-detected if omitted.
tag_audio_eventsNoTag non-speech audio events (laughter, music, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv5.8.0
    • addedInput schema / properties / estimate_only
      Added value: +{
+  "description": "Return the estimated credit cost WITHOUT submitting anything. Use before expensive runs (video, 4K, 1080p upgrades, layer splits).",
+  "type": "boolean"
+}
    • addedInput schema / properties / max_credits
      Added value: +{
+  "description": "Refuse to submit if the estimated cost exceeds this many credits (overrides KIE_MAX_CREDITS_PER_CALL). Estimates come from published rates; kie bills the actual amount.",
+  "type": "number"
+}
  2. First observedv4.7.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the model and that diarization/event tagging are supported, but says nothing about whether the call is synchronous or returns a task id for check_task, credit cost, audio length/format limits, or failure modes — all material for a 6-parameter media tool.

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?

Three short sentences, front-loaded with the core action and engine, then capabilities, then return type. With no output schema present, the 'Returns transcription text' line earns its place rather than repeating structured data.

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 tool with no annotations and no output schema, the description covers purpose, engine, optional features, and return type adequately. It omits the async/task lifecycle (check_task exists as a sibling), cost behavior, and input constraints, leaving real gaps for an agent invoking it.

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 each of the 6 parameters is already documented, giving a baseline of 3. The description restates two of them (diarization, audio event tagging) without adding syntax, defaults, or interaction rules, so it does not rise above the schema.

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?

States a specific verb+resource ('Transcribe audio to text') and names the underlying engine (ElevenLabs Scribe v1), which unambiguously separates it from the text-to-speech siblings like generate_tts. It stops short of explicitly contrasting with any named sibling or stating scope limits (duration, size), so it lands just under 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 gives no when-to-use or when-not-to-use guidance and names no alternatives. Useful routing hints such as 'use estimate_only before expensive runs' exist only in the schema property text, not in the description the agent sees first.

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