Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_environment_variable

Define an environment variable to manage environment-specific authentication connections for the ElevenLabs API, requiring a unique label and a 'production' key.

Instructions

Create Environment Variable

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_environment_variable"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNo
labelNoUnique label for the environment variable.
valuesNoEnvironment-specific auth connection references. Must include 'production' key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already disclose that this is a non-read-only, non-idempotent, open-world, non-destructive write. The description adds nothing beyond that — no mention of required permissions, what happens on duplicate labels, or how auth connection references are created.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single phrase is technically brief but it is under-specification rather than conciseness; it omits any front-loaded useful information about the operation.

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

Completeness1/5

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

For a mutation tool with a nested 'values' object, an undocumented 'type' parameter, no required-parameter guidance, and no output schema, the description is completely inadequate — an agent cannot safely call this correctly from the given text.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, with 'label' and 'values' documented but the 'type' parameter carrying no description and no enum. The description provides zero parameter information, so it fails to compensate for the undocumented 'type' field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Create Environment Variable' merely restates the tool name and title verbatim, adding no scope, target, or distinguishing detail. It does not differentiate this tool from siblings like update_environment_variable, get_environment_variable, or list_environment_variables.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

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

There is no guidance on when to use this tool, what prerequisites exist, or how it relates to alternatives such as update_environment_variable. The agent is left to infer everything from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools