Skip to main content
Glama

assemblyai_transcribe

Transcribe audio or video files with AssemblyAI, enabling speaker diarization, summarization, sentiment analysis, and entity detection for comprehensive analysis.

Instructions

Submit an audio or video file for transcription with AssemblyAI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyYesAssemblyAI API key from assemblyai.com/dashboard
audio_urlYesPublicly accessible URL of the audio/video file
language_codeNoLanguage code (e.g. en, es, fr, de). Omit for auto-detection.
language_detectionNoEnable automatic language detection
speaker_labelsNoEnable speaker diarization
auto_chaptersNoGenerate auto chapters
summarizationNoGenerate a summary (also set summary_type)
summary_typeNoSummary format
sentiment_analysisNoEnable sentiment analysis per sentence
entity_detectionNoEnable named entity detection
punctuateNoAdd punctuation (default: true)
format_textNoFormat text with capitalisation
webhook_urlNoURL to POST transcript results to when complete
Behavior2/5

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

No annotations; description merely states 'submit', omitting that transcription is asynchronous and returns a transcript ID for later retrieval via other tools.

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

Conciseness4/5

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

Single concise sentence, but front-loads purpose; slight over-conciseness given tool complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 13 parameters, async behavior, and no output schema; description insufficient for complete understanding. Lacks mention of how to use results.

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 baseline 3; description adds no extra meaning to parameters beyond 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?

Clear verb 'Submit' and resource 'audio or video file for transcription with AssemblyAI' distinguishes from sibling tools like assemblyai_get_transcript.

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?

No guidance on when to use vs. sibling tools (e.g., get transcript after submission), no context on prerequisites or limitations.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/malamutemayhem/unclick'

If you have feedback or need assistance with the MCP directory API, please join our Discord server