Skip to main content
Glama

remix_audio

Create a remix of an audio track by specifying a URL and remix style to transform music with AI-powered audio processing.

Instructions

Create a remix of an audio track

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesURL of the audio file to remix
remix_styleNoStyle of remix to create
webhook_urlNoURL for callback upon completion

Implementation Reference

  • The handler function that implements the core logic for the 'remix_audio' tool. It validates input, calls the MusicGPT API endpoint '/remix', and returns the task information with instructions for status checking.
    private async handleRemixAudio(args: any) {
      if (!args.audio_url) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url is required");
      }
    
      const response = await this.axiosInstance.post("/remix", {
        audio_url: args.audio_url,
        remix_style: args.remix_style,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Audio remix started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • src/index.ts:423-444 (registration)
    The tool registration entry in the TOOLS array, which includes the name, description, and input schema. This is returned by the list tools handler.
    {
      name: "remix_audio",
      description: "Create a remix of an audio track",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the audio file to remix",
          },
          remix_style: {
            type: "string",
            description: "Style of remix to create",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url"],
      },
    },
  • src/index.ts:703-704 (registration)
    The switch case in the main tool execution handler that routes calls to the 'remix_audio' tool to its specific handler function.
    case "remix_audio":
      return await this.handleRemixAudio(args);
  • The input schema definition for the 'remix_audio' tool, defining parameters like audio_url (required), remix_style, and webhook_url.
    inputSchema: {
      type: "object" as const,
      properties: {
        audio_url: {
          type: "string",
          description: "URL of the audio file to remix",
        },
        remix_style: {
          type: "string",
          description: "Style of remix to create",
        },
        webhook_url: {
          type: "string",
          description: "URL for callback upon completion",
        },
      },
      required: ["audio_url"],
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'create a remix' implying a generative/mutation operation, but doesn't disclose behavioral traits like whether it's asynchronous (suggested by webhook_url), requires specific permissions, has rate limits, or what the output entails. This is a significant gap for a tool with potential complexity.

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, efficient sentence with zero waste. It's front-loaded with the core purpose, making it easy to parse quickly, which is ideal for conciseness.

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?

Given no annotations, no output schema, and a tool that likely involves asynchronous processing (implied by webhook_url), the description is incomplete. It doesn't explain the return values, error handling, or behavioral context, leaving gaps for an AI agent to understand how to use it effectively.

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. The description doesn't add meaning beyond the schema (e.g., explaining remix_style options or webhook_url usage), resulting in a baseline score of 3 where the schema does the heavy lifting.

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 action ('create a remix') and resource ('of an audio track'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create_cover_song' or 'voice_changer' which also transform audio, missing specific distinction.

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 is provided on when to use this tool versus alternatives. With many sibling tools for audio processing (e.g., 'create_cover_song', 'voice_changer'), the description lacks context on appropriate scenarios or exclusions, leaving usage ambiguous.

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