Skip to main content
Glama

transcribe_audio

Convert speech in audio files to text for transcription, supporting multiple languages and optional webhook notifications.

Instructions

Transcribe speech from audio to text

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesURL of the audio file to transcribe
languageNoLanguage code (e.g., 'en', 'es', 'fr')
webhook_urlNoURL for callback upon completion

Implementation Reference

  • The handler function that implements the core logic of the transcribe_audio tool by making an API call to /audiotranscribe endpoint.
    private async handleTranscribeAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/audiotranscribe", {
        audio_url: args.audio_url,
        language: args.language,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio transcription started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • Input schema defining parameters for the transcribe_audio tool including audio_url (required), language, and webhook_url.
    inputSchema: {
      type: "object" as const,
      properties: {
        audio_url: {
          type: "string",
          description: "URL of the audio file to transcribe",
        },
        language: {
          type: "string",
          description: "Language code (e.g., 'en', 'es', 'fr')",
        },
        webhook_url: {
          type: "string",
          description: "URL for callback upon completion",
        },
      },
      required: ["audio_url"],
    },
  • src/index.ts:522-542 (registration)
    Tool registration object in the TOOLS array that defines the tool's metadata and schema for MCP list tools request.
      name: "transcribe_audio",
      description: "Transcribe speech from audio to text",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to transcribe",
          },
          language: {
            type: "string",
            description: "Language code (e.g., 'en', 'es', 'fr')",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url"],
      },
    },
  • src/index.ts:713-714 (registration)
    Switch case in the CallTool request handler that registers and routes transcribe_audio calls to its handler function.
    case "transcribe_audio":
      return await this.handleTranscribeAudio(args);
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 burden of behavioral disclosure. While 'Transcribe' implies a read/transform operation, the description doesn't mention whether this is synchronous or asynchronous (though webhook_url suggests async), what permissions are needed, rate limits, supported audio formats, or error conditions. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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 perfectly concise at 5 words, front-loading the core purpose immediately. Every word earns its place with zero waste or redundancy. The structure is optimal for quick comprehension while being complete enough to understand the basic function.

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?

For a tool with no annotations, no output schema, and multiple parameters, the description is insufficiently complete. It doesn't explain what format the transcription returns, whether it's synchronous or asynchronous (webhook_url implies async but isn't explained), what audio formats are supported, or error handling. The agent would need to guess about important operational aspects.

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 schema already documents all three parameters thoroughly. The description adds no additional parameter information beyond what's in the schema. The baseline score of 3 reflects adequate parameter documentation through the schema alone, though the description contributes nothing extra.

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 clearly states the verb ('Transcribe') and resource ('speech from audio to text'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'text_to_speech' or 'extract_audio', which could cause confusion about when to use this specific transcription tool versus other audio processing options.

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 provides no guidance on when to use this tool versus alternatives. With 23 sibling tools including 'text_to_speech' (reverse operation) and 'extract_audio' (similar audio processing), the agent receives no help distinguishing this transcription tool from other audio-related operations. No context about appropriate use cases is provided.

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/pasie15/mcp-server-musicgpt'

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