Skip to main content
Glama

transcription

by com.scriptivox.www

transcription_url

[DEPRECATED — use transcribe_url instead] Alias kept for backward compatibility with @scriptivox/mcp-server@1.0.x. Will be removed in 2.0.0. Identical behavior to transcribe_url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesPublic URL to an audio/video file (http/https).
alignNoWord-level timestamps + confidence scores. Default: true. Pass false to opt out (ignored when diarize: true).
diarizeNoEnable speaker diarization. Default: false. When true, word-level alignment is automatically enabled regardless of `align`.
languageNoISO 639-1 language code (e.g. "en", "es", "fr"). 119 languages supported. Strongly recommended when you know the language.
webhook_urlNoOptional HTTPS URL where transcription.* events will be POSTed (HMAC-signed).
speaker_countNoExpected number of speakers (1-50). Requires diarize: true. Passing this when known improves diarization accuracy.
await_completedNoDefault: true. When false, return the transcription_id immediately without polling.
idempotency_keyNoOptional Idempotency-Key header (up to 255 chars). Same key + same body = same transcription_id.

TDQS

A3.9/5.0
Behavior3/5

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

The description adds lifecycle behavior: deprecation, backward-compatibility scope, and removal version. However, it delegates all runtime behavior to transcribe_url and does not disclose side effects, return behavior, or async characteristics beyond what the schema hints at.

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 a single compact sentence that leads with the deprecation warning and alternative before explaining compatibility and removal. Every clause earns its place with no redundancy.

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 deprecated alias, pointing to transcribe_url and covering all parameters via schema is largely sufficient. Still, with no output schema and no mention of return values or event behavior, an agent encountering this tool alone would need to inspect transcribe_url for complete operational context.

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 the parameters are already fully documented. The description adds no parameter-level semantics, which is acceptable but not helpful beyond the baseline.

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 immediately identifies the tool as a deprecated alias for transcribe_url and states 'Identical behavior to transcribe_url', which establishes the action and resource by reference. The annotation title 'Transcribe from URL' adds basic purpose, though actual behavior is not independently described.

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

Usage Guidelines5/5

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

The description explicitly says to use transcribe_url instead, marks the tool as deprecated, and states removal plans. This is unambiguous when-to-use versus when-not-to-use guidance, with the alternative named directly.

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

All transcription toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

The set contains several near-neighbor groups: deprecated aliases duplicate live tools, and docs/billing/financial tools have fuzzy boundaries. Individual descriptions are detailed and resolve most collisions, but matching the right tool among 39 still requires care.

Naming Consistency3/5

Most tools follow a sensible verb_object style, but the transcribe_* group is inconsistent: transcribe_url/transcribe_upload are verb_object, while transcribe_status/transcribe_cancel/transcribe_delete are really status/cancel/delete operations renamed with a transcribe prefix. The deprecated transcription_status/transcription_url aliases add another naming convention, so the pattern is not reliable across the set.

Tool Count2/5

39 tools is well over the 25+ threshold and creates an overwhelmingly broad surface spanning account management, billing, docs, API jobs, library organization, meeting bots, and automations. Two deprecated duplicates inflate the count further. This would be more coherent split into separate servers or at least pruned of deprecated aliases.

Completeness3/5

Core API transcription lifecycle is covered, and the library/meeting-bot flows have search, tagging, moving, and audio retrieval. However, there is no user-library deletion/rename, no OAuth-side full-transcript access, local upload is non-functional over the hosted endpoint, and webhook management is documented but not exposed as tools. These gaps force agents to work around missing operations.

Resources