Skip to main content
Glama

transcription

by com.scriptivox.www

transcribe_upload

Transcribe a LOCAL file by uploading it to Scriptivox. NOT AVAILABLE over the hosted MCP endpoint: this server has no access to your filesystem. Use transcribe_url with a public URL, run @scriptivox/mcp-server locally over stdio, or drive the 3-step REST upload flow yourself. Max file size 5 GB. Requires a configured API key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
file_pathYesAbsolute path to the audio/video file on the local filesystem.
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

A4.6/5.0
Behavior4/5

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

Annotations already mark this as non-read-only and non-destructive; the description adds the filesystem-access limitation, a 5 GB max file size, and the configured API-key requirement. It does not contradict the annotations, though it leaves longer-running/asynchronous outcomes to the await_completed parameter rather than stating them up front.

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 compact and front-loaded: the core purpose and the most important warning appear in the first sentence, followed by actionable alternatives and constraints. Every sentence earns its place and there is no filler.

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 an 8-parameter upload tool, the description plus schema provide nearly everything: local-only constraint, max size, auth, alternatives, and parameter semantics. It stops just short of fully explaining the return/result shape and the potential long-running nature of the operation, which would be especially useful given there is no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema covers all 8 parameters, so the baseline is 3; the description goes further by adding the 5 GB file-size ceiling and emphasizing that file_path must be a local file visible to the server. This is material constraint information not present in the schema.

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?

The description names the exact operation and target: 'Transcribe a LOCAL file by uploading it to Scriptivox.' The explicit contrast with transcribe_url immediately distinguishes this tool from its closest sibling.

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?

It states the key exclusion ('NOT AVAILABLE over the hosted MCP endpoint: this server has no access to your filesystem'), then gives the concrete alternatives: transcribe_url, running the server locally over stdio, or the REST upload flow. It also states the API-key prerequisite, so an agent knows exactly when this tool is usable.

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