Skip to main content
Glama

list_voices

Explore and retrieve all available voice options for text-to-speech and voice cloning services within the MiniMax MCP JS environment. Specify voice types to filter results.

Instructions

List all available voices. Only supported when api_host is https://api.minimax.chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voiceTypeNoType of voices to list, values: ["all", "system", "voice_cloning"]all

Implementation Reference

  • Handler function for the 'list_voices' MCP tool. Calls voiceApi.listVoices(params) and returns formatted success or error message.
    async (params) => {
      try {
        // No need to update configuration from request parameters in stdio mode
        const result = await this.voiceApi.listVoices(params);
    
        return {
          content: [
            {
              type: 'text',
              text: `Success. System voices: ${result.systemVoices.join(', ')}, Cloned voices: ${result.voiceCloneVoices.join(', ')}`,
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Failed to list voices: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
        };
      }
    },
  • Registers the 'list_voices' tool with the MCP server, including description, input schema using Zod, and the handler function.
    private registerListVoicesTool(): void {
      this.server.tool(
        'list_voices',
        'List all available voices. Only supported when api_host is https://api.minimax.chat.',
        {
          voiceType: z
            .string()
            .optional()
            .default('all')
            .describe('Type of voices to list, values: ["all", "system", "voice_cloning"]'),
        },
        async (params) => {
          try {
            // No need to update configuration from request parameters in stdio mode
            const result = await this.voiceApi.listVoices(params);
    
            return {
              content: [
                {
                  type: 'text',
                  text: `Success. System voices: ${result.systemVoices.join(', ')}, Cloned voices: ${result.voiceCloneVoices.join(', ')}`,
                },
              ],
            };
          } catch (error) {
            return {
              content: [
                {
                  type: 'text',
                  text: `Failed to list voices: ${error instanceof Error ? error.message : String(error)}`,
                },
              ],
            };
          }
        },
      );
    }
  • TypeScript interface defining the input parameters for list_voices request.
    export interface ListVoicesRequest {
      voiceType?: string;
    }
  • VoiceAPI.listVoices method: Makes API call to MiniMax /v1/get_voice endpoint, processes response, formats voice lists, and returns structured data used by the tool handler.
    async listVoices(request: ListVoicesRequest = {}): Promise<{ systemVoices: string[], voiceCloneVoices: string[] }> {
      try {
        // Send request
        const response = await this.api.post<any>('/v1/get_voice', {
          voice_type: request.voiceType || 'all'
        });
    
        // Process response
        const systemVoices = response?.system_voice || [];
        const voiceCloneVoices = response?.voice_cloning || [];
    
        // Format voice information
        const systemVoiceList: string[] = [];
        const voiceCloneVoiceList: string[] = [];
    
        for (const voice of systemVoices) {
          systemVoiceList.push(`Name: ${voice.voice_name}, ID: ${voice.voice_id}`);
        }
    
        for (const voice of voiceCloneVoices) {
          voiceCloneVoiceList.push(`Name: ${voice.voice_name}, ID: ${voice.voice_id}`);
        }
    
        return {
          systemVoices: systemVoiceList,
          voiceCloneVoices: voiceCloneVoiceList
        };
      } catch (error) {
        throw new MinimaxRequestError(`Failed to list voices: ${String(error)}`);
      }
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds context about the api_host requirement, which is useful beyond the basic 'list' function. However, it doesn't describe other behavioral traits such as rate limits, authentication needs, or what the return format looks like (e.g., pagination, structure), leaving gaps in transparency.

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 appropriately sized and front-loaded, consisting of two concise sentences that directly state the tool's purpose and a key constraint. There is no wasted language, and every sentence earns its place by providing essential information efficiently.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It covers the basic purpose and a constraint, but without annotations or an output schema, it doesn't fully explain behavioral aspects or return values, making it adequate but not comprehensive for 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?

The input schema has 100% description coverage, with the 'voiceType' parameter fully documented in the schema itself. The description doesn't add any meaning beyond what the schema provides, as it doesn't mention parameters at all. According to the rules, when schema coverage is high (>80%), the baseline score is 3, which applies here.

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 ('List') and resource ('all available voices'), making it immediately understandable. However, it doesn't differentiate this tool from potential sibling tools like 'voice_design' or 'voice_clone', which might also involve voice-related operations, 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides some usage guidance by specifying that the tool is 'Only supported when api_host is https://api.minimax.chat,' which implies a prerequisite condition. However, it doesn't explicitly state when to use this tool versus alternatives like 'voice_clone' or 'voice_design', nor does it provide clear exclusions or comparisons with siblings, leaving usage context partially implied.

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

Related 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/MiniMax-AI/MiniMax-MCP-JS'

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