Skip to main content
Glama

change_audio_speed

Adjust audio playback speed by applying a speed multiplier to audio files. Modify tempo for faster or slower listening without altering pitch.

Instructions

Change the playback speed of audio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesURL of the audio file to process
speed_factorYesSpeed multiplier (e.g., 1.5 for 1.5x speed, 0.75 for 0.75x speed)
webhook_urlNoURL for callback upon completion

Implementation Reference

  • The handler function that implements the core logic for the 'change_audio_speed' tool. It validates input parameters, makes a POST request to the '/audio_speed_changer' API endpoint with the provided audio_url, speed_factor, and optional webhook_url, and returns a response message including the task_id for status checking.
    private async handleChangeAudioSpeed(args: any) {
      if (!args.audio_url || !args.speed_factor) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url and speed_factor are required");
      }
    
      const response = await this.axiosInstance.post("/audio_speed_changer", {
        audio_url: args.audio_url,
        speed_factor: args.speed_factor,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio speed change 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 the parameters for the 'change_audio_speed' tool: required audio_url (string) and speed_factor (number), optional webhook_url (string). Used for validation and tool description.
    inputSchema: {
      type: "object" as const,
      properties: {
        audio_url: {
          type: "string",
          description: "URL of the audio file to process",
        },
        speed_factor: {
          type: "number",
          description: "Speed multiplier (e.g., 1.5 for 1.5x speed, 0.75 for 0.75x speed)",
        },
        webhook_url: {
          type: "string",
          description: "URL for callback upon completion",
        },
      },
      required: ["audio_url", "speed_factor"],
    },
  • src/index.ts:383-404 (registration)
    Tool registration entry in the TOOLS array, which is returned by the ListTools handler. Includes name, description, and input schema.
    {
      name: "change_audio_speed",
      description: "Change the playback speed of audio",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to process",
          },
          speed_factor: {
            type: "number",
            description: "Speed multiplier (e.g., 1.5 for 1.5x speed, 0.75 for 0.75x speed)",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url", "speed_factor"],
      },
    },
  • src/index.ts:699-700 (registration)
    Switch case in the CallToolRequestSchema handler that routes calls to 'change_audio_speed' to the specific handleChangeAudioSpeed method.
    case "change_audio_speed":
      return await this.handleChangeAudioSpeed(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'change' implies a mutation, it doesn't specify whether this is a destructive operation, what permissions are needed, whether it processes locally or via API, or what happens upon completion (e.g., returns processed audio or just confirmation). The mention of 'playback speed' suggests it might be a non-destructive effect, but this isn't explicit.

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, clear sentence that states the core functionality without any fluff. It's perfectly front-loaded and wastes no words, making it easy for an agent to parse quickly.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what the tool returns (e.g., a modified audio file, a processing ID, or just a confirmation), doesn't mention error conditions or limitations, and provides no behavioral context. Given the complexity of audio processing and lack of structured data, more completeness is needed.

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?

The description adds no parameter information beyond what's already in the schema (which has 100% coverage). It doesn't explain the relationship between parameters (e.g., that 'webhook_url' is optional for asynchronous processing) or provide additional context about valid ranges for 'speed_factor'. With high schema coverage, the baseline score of 3 is appropriate.

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 tool's purpose with a specific verb ('change') and resource ('playback speed of audio'), making it immediately understandable. However, it doesn't differentiate from sibling tools like 'remix_audio' or 'extend_audio' which might also affect audio playback characteristics, so it doesn't reach the highest score.

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 many sibling tools that manipulate audio (e.g., 'remix_audio', 'extend_audio', 'cut_audio'), there's no indication of when speed adjustment is appropriate versus other transformations, leaving the agent without usage context.

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