Skip to main content
Glama
Sign In

ImgKits MCP

by io.github.yichong1
OverviewDiscussionsAdmin

Transcribe audio (Faster-Whisper)

transcribe_audio

Transcribe a public audio URL via Faster-Whisper (async create + result poll; no status endpoint). Pass audio_url (http(s)) to start or job_id to poll. Optional language, response_format (simple|raw). Empty transcript is still success (no speech detected). Cost: 2 credits per call. Compliance / SSRF: Use only on material you own or are explicitly licensed/authorized to generate or remix. Do not generate or redistribute copyrighted music, voice likenesses, or trademarked audio without permission. Output URLs have a limited TTL and must not be abused for bulk scraping or redistribution. Calls are rate-limited/metered by mcp-credit-gateway and require a valid sk_live_ key. （仅处理自有或已获授权素材；禁止滥用生成/二创他人受版权保护的音乐或声音；输出有 TTL；调用限频。）

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_audio"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idNoExisting Faster-Whisper job id. Polling never creates a new upstream job.
languageNoOptional language code (e.g. `en`, `zh`). Omit for auto-detect.
audio_urlNoPublic http(s) URL of the audio to transcribe (<= 2048 chars). Required to start a new job; omit when polling with `job_id` only.
wait_secondsNoHow long to wait for a result, 0–55 seconds (default 30).
idempotency_keyNoOptional caller correlation key. Billing is handled by mcp-credit-gateway.
response_formatNoUpstream response format: `simple` (default) or `raw`.simple

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

Adds substantial behavior beyond annotations: the async job lifecycle with no status endpoint, that an empty transcript is still a success, a cost of 2 credits per call, rate limiting/metering via mcp-credit-gateway with an sk_live_ key requirement, and limited-TTL output URLs. These are exactly the operational facts the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false) do not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the two operating modes are front-loaded, which is good, but the compliance block is long and then repeated verbatim in a Chinese parenthetical, which is pure duplication. The policy content could be compressed to a single sentence without losing meaning.

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?

For a 6-parameter async job tool with no output schema it covers the lifecycle, cost, TTL, and auth prerequisites, which is most of what an agent needs. It does not describe what the transcript payload contains or how long jobs/results persist, leaving a modest 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 coverage is 100%, so all six parameters are already documented, including the audio_url/job_id mutual exclusivity and wait_seconds defaults. The description restates `audio_url`, `job_id`, `language`, and `response_format` without adding format or syntax detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('transcribe a public audio URL') plus the underlying engine (Faster-Whisper) and its interaction model ('async create + result poll; no status endpoint'). An agent can distinguish this from siblings like generate_subtitles or detect_language without opening a schema.

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

Usage Guidelines4/5

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

Gives explicit mode-selection guidance: pass `audio_url` to start, `job_id` to poll, and notes the licensing/ownership precondition for legitimate use. It stops short of naming alternatives (e.g., when to prefer generate_subtitles or translate_subtitle instead), so no exclusions are stated.

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

All ImgKits MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources