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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_service_account

Create a new service account for programmatic ElevenLabs access, optionally assigning default sharing groups to control resource visibility.

Instructions

Create Service Account

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
default_sharing_groupsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the mutation and open-world nature is captured structurally. The description adds nothing further — no note on required permissions, what the created account can do, or whether default_sharing_groups grants access.

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?

Three words that mirror the title, which is under-specification rather than conciseness. There is no front-loaded content because there is no content.

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?

A mutation tool with no output schema, undocumented parameters (including a nested free-form array), and no sibling differentiation is left entirely described by its name. An agent cannot know what this account is, what it can access, or what identifies it on return.

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

Parameters1/5

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

Schema description coverage is 0% for two parameters, yet the description says nothing about 'name' or 'default_sharing_groups'. The meaning of default_sharing_groups — an array of free-form objects with additionalProperties unconstrained — is completely opaque and unmitigated by any text.

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 Service Account' is a verbatim restatement of the tool name and title, adding no information beyond what the identifier already conveys. It does not distinguish this tool from close siblings such as create_service_account_api_key or get_workspace_service_accounts.

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 is provided. The crowded sibling namespace (create_service_account_api_key, edit_service_account_api_key, delete_service_account_api_key) makes the absence of routing guidance costly.

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