Skip to main content
Glama
AiAgency-Now

VoiceAI-MCP-VAVicky

Official
by AiAgency-Now
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

update_elevenlabs_token

Update the ElevenLabs API key for VoiceAI-MCP-VAVicky to maintain access to voice generation services.

Instructions

Update Elevenlabs API Key

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
elevenlabs_tokenYesElevenlabs API Key

Implementation Reference

  • index.js:523-527 (handler)
    The handler logic in the executeTool method's switch statement. It sets up a POST request to the backend API endpoint `/elevenlabs/oauth` with the provided elevenlabs_token in the body.
    case 'update_elevenlabs_token':
  url = `${this.baseUrl}/elevenlabs/oauth`;
  method = 'POST';
  body = { elevenlabs_token: args.elevenlabs_token };
  break;
  • index.js:90-100 (schema)
    Defines the input schema for the tool, specifying that it requires an 'elevenlabs_token' string parameter. This is part of the tool list returned by the ListToolsRequestSchema handler.
    {
  name: 'update_elevenlabs_token',
  description: 'Update Elevenlabs API Key',
  inputSchema: {
    type: 'object',
    properties: {
      elevenlabs_token: { type: 'string', description: 'Elevenlabs API Key' }
    },
    required: ['elevenlabs_token']
  }
},
  • index.js:90-100 (registration)
    The tool is registered by including it in the list of available tools returned by the ListToolsRequestSchema handler.
    {
  name: 'update_elevenlabs_token',
  description: 'Update Elevenlabs API Key',
  inputSchema: {
    type: 'object',
    properties: {
      elevenlabs_token: { type: 'string', description: 'Elevenlabs API Key' }
    },
    required: ['elevenlabs_token']
  }
},

Tool Definition Quality

C2.9/5.0
Behavior2/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. 'Update' implies a mutation operation, but it doesn't specify whether this requires admin permissions, if it overwrites existing tokens, what happens on success/failure, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with just three words, front-loading the essential action and resource. There's zero waste or redundancy, making it efficient for quick comprehension.

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 insufficient. It doesn't explain what the update entails (e.g., persistence, scope), potential side effects, or expected outcomes, leaving significant gaps in understanding the tool's behavior.

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 parameter is well-documented in the schema. The description doesn't add any meaning beyond what the schema provides (e.g., format requirements, validation rules, or usage examples), which aligns with the baseline score when schema coverage is high.

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 ('Update') and resource ('Elevenlabs API Key'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like update_deepseek_token or update_openai_token, which follow the same pattern for different services.

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, prerequisites, or context. It doesn't mention why someone would update this token versus others (e.g., update_openai_token) or what triggers this need.

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/AiAgency-Now/MCP-VoiceAI-WhiteLabel'

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