Skip to main content
Glama

ElevenLabs

by io.github.mcp-dir

elevenlabs_invite_users_bulk

Invite Multiple Users. Sends email invitations to join your workspace to the provided emails. Requires all email addresses to be part of a verified domain. If the users don't have an account they will be prompted to create one. If the users accept these invites they will be added as users to your workspace and your subscription using one of your seats. This endpoint may only be called by workspace members with the WORKSPACE_MEMBERS_INVITE permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailsYes
accountNo
group_idsNo
seat_typeNo
usage_limitNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing key behavioral traits: the verified domain requirement, the automatic account creation prompt for new users, the consumption of a workspace seat upon acceptance, and the required permission. This adds substantial context that annotations alone do not provide.

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

Conciseness4/5

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

The description is front-loaded with 'Invite Multiple Users' and uses four sentences, each adding meaningful information (emails, domain requirement, account creation, seat usage, permissions). It is not overly verbose and earns its place without unnecessary fluff.

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?

The description covers the core purpose, prerequisites, and consequences of accepting invitations, which is good for a bulk action tool. However, it lacks details on the remaining parameters and does not mention the response format or whether the operation is synchronous, given there is no output schema. This leaves some gaps for a tool with 5 parameters.

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?

The schema has 5 parameters but 0% description coverage, so the description must compensate. It only refers to 'provided emails' for the emails parameter and does not explain account, group_ids, seat_type, or usage_limit. This leaves the agent without enough information to correctly populate non-required parameters.

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

Purpose5/5

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

The description clearly states 'Invite Multiple Users' and explains that it sends email invitations to join your workspace for the provided emails. This distinguishes it from the sibling tool elevenlabs_invite_user which handles single-user invitations, and the verb 'invite' plus the plural 'users' makes the purpose unmistakable.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: for bulk invitations to a workspace. It also mentions prerequisites (verified domain, WORKSPACE_MEMBERS_INVITE permission) and what happens upon acceptance (users added to workspace and subscription). However, it does not explicitly state alternatives or exclusions, such as 'use elevenlabs_invite_user for a single invitation'.

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

All ElevenLabs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

C2.4/5.0
Disambiguation2/5

There are many tools with overlapping purposes, such as multiple voice retrieval tools (get_voice_by_id, get_voices, get_user_voices_v2, get_library_voices) and several dubbing transcript segment editors with only subtle naming differences. The inclusion of platform-level tools (authenticate, connect, marketplace) alongside ElevenLabs API tools further blurs boundaries.

Naming Consistency1/5

Naming is highly inconsistent. Most tools have the 'elevenlabs_' prefix, but some do not (authenticate, connect, marketplace, report_bug, show_version, toolkit_info). Several tools have truncated/random suffix names (e.g., elevenlabs_dubbing_target_transcript_segmen_b565e6, elevenlabs_get_pronunciation_dictionary_ver_45baf2), and one tool is in Portuguese (elevenlabs_list_accounts). This mixture of conventions and languages makes the pattern unpredictable.

Tool Count1/5

With 155 tools, the server is extremely bloated. It mixes a comprehensive ElevenLabs API surface with unrelated MCP platform tools (marketplace, authenticate, report_bug, etc.) that belong in a separate toolkit. This is a severe mismatch between the apparent purpose (ElevenLabs audio services) and the sheer number of tools.

Completeness3/5

The ElevenLabs-specific tools cover a wide range of operations (text-to-speech, voice management, dubbing, pronunciation dictionaries, Studio projects, workspace administration, order management), making it fairly complete for those domains. However, the inclusion of unrelated platform tools and the lack of a clear focus mean that an agent would have difficulty navigating this large surface, and some operations like music finetuning or speech engines appear only partially covered.

Resources