Delete Workspace Auth Connection. Delete an auth connection
Bulk support: accepts auth_connection_ids for batched execution.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| auth_connection_id | Yes | ||
| auth_connection_ids | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'Delete' which is a destructive action, but the annotation destructiveHint is false. This contradicts the annotation. Additionally, the description provides no behavioral details beyond the action itself, such as consequences, reversibility, or permissions, which is especially important given the sparse annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of two short sentences. However, the first sentence redundantly repeats 'Delete an auth connection' after 'Delete Workspace Auth Connection', wasting words. It is still appropriately front-loaded and no extraneous content appears.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple delete tool with three parameters and no output schema, the description provides the core action and bulk capability. However, it omits details about the 'account' parameter, lacks guidance on parameter choices, and fails to mention any side effects or prerequisites. While adequate for a minimal understanding, it is not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It only mentions 'auth_connection_id' and 'auth_connection_ids' for bulk support, but does not clarify their relationship or explain the 'account' parameter at all. The meaning of parameters is largely inferred from names, and the description adds minimal semantic value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: deleting an auth connection from a workspace, with an explicit verb and resource. It distinguishes itself from sibling tools like elevenlabs_create_auth_connection, elevenlabs_update_auth_connection, and elevenlabs_list_auth_connections by explicitly naming the delete operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage (when you need to delete an auth connection) but does not explicitly state when to use this tool versus alternatives. It mentions bulk support but does not clarify the distinction between single and batch deletion or provide any exclusionary guidance. No alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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 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.
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.
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.