Skip to main content
Glama

create_cover_song

Transform songs into cover versions by applying different vocal styles or voices to original audio files using AI-powered voice conversion.

Instructions

Create a cover version of a song with a different voice or style

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
audio_urlYesURL of the original audio file
voice_idYesVoice model ID to use for the cover (use get_all_voices to find IDs)
webhook_urlNoURL for callback upon completion

Implementation Reference

  • The handler function that implements the core logic for the 'create_cover_song' tool. It validates inputs, makes a POST request to the MusicGPT API '/cover' endpoint, and returns the task details with instructions for status checking.
    private async handleCreateCover(args: any) {
      if (!args.audio_url || !args.voice_id) {
        throw new McpError(ErrorCode.InvalidParams, "audio_url and voice_id are required");
      }
    
      const response = await this.axiosInstance.post("/cover", {
        audio_url: args.audio_url,
        voice_id: args.voice_id,
        webhook_url: args.webhook_url,
      });
    
      return {
        content: [
          {
            type: "text",
            text: `Cover song creation started!\n\n${JSON.stringify(response.data, null, 2)}\n\nUse get_conversion_by_id with the task_id to check the status.`,
          },
        ],
      };
    }
  • The input schema defining parameters for the create_cover_song tool: required audio_url and voice_id, optional webhook_url.
    inputSchema: {
      type: "object" as const,
      properties: {
        audio_url: {
          type: "string",
          description: "URL of the original audio file",
        },
        voice_id: {
          type: "string",
          description: "Voice model ID to use for the cover (use get_all_voices to find IDs)",
        },
        webhook_url: {
          type: "string",
          description: "URL for callback upon completion",
        },
      },
      required: ["audio_url", "voice_id"],
    },
  • src/index.ts:161-182 (registration)
    The tool definition object in the TOOLS array, which is returned by the listTools handler, registering the tool's name, description, and schema.
    {
      name: "create_cover_song",
      description: "Create a cover version of a song with a different voice or style",
      inputSchema: {
        type: "object" as const,
        properties: {
          audio_url: {
            type: "string",
            description: "URL of the original audio file",
          },
          voice_id: {
            type: "string",
            description: "Voice model ID to use for the cover (use get_all_voices to find IDs)",
          },
          webhook_url: {
            type: "string",
            description: "URL for callback upon completion",
          },
        },
        required: ["audio_url", "voice_id"],
      },
    },
  • src/index.ts:671-672 (registration)
    The switch case in the CallToolRequestSchema handler that routes calls to the create_cover_song tool to its handler function.
    case "create_cover_song":
      return await this.handleCreateCover(args);
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without disclosing behavioral traits such as processing time, output format, error handling, or rate limits. It mentions a webhook for completion but doesn't detail what happens during processing or on failure.

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 that front-loads the core purpose without unnecessary words. Every part earns its place by clearly stating the tool's 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?

Given the complexity of audio processing with no annotations and no output schema, the description is insufficient. It lacks details on what the tool returns, how errors are handled, or any constraints, making it incomplete for effective agent use.

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 parameters. The description adds no additional meaning beyond the schema, such as explaining how the voice_id affects style or what audio formats are supported. Baseline 3 is appropriate as 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 tool's purpose with a specific verb ('create') and resource ('cover version of a song'), specifying it involves different voice or style. It distinguishes from siblings like 'voice_changer' or 'sing_over_instrumental' by focusing on cover creation, but doesn't explicitly differentiate them.

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 this tool versus alternatives like 'voice_changer' or 'sing_over_instrumental' is provided. The description implies usage for cover songs but lacks context on prerequisites, exclusions, or comparisons with sibling tools.

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