elevenlabs_get_workspace_webhooks_route
Read-onlyIdempotent
List Workspace Webhooks. List all webhooks for a workspace
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| include_usages | No |
ElevenLabs
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds little beyond that, and it does not describe whether include_usages affects response size, workspace scoping behavior, or pagination.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short, but the second sentence largely restates the first. While there is no verbosity problem, the redundancy means the second sentence does not earn its place.
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?
This is a simple read-only listing tool with helpful annotations, but no output schema exists and the two parameters are unexplained. The description says 'all webhooks' but does not clarify account context or what include_usages adds, making it minimally adequate rather than complete.
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% and the description does not explain either 'account' or 'include_usages'. The agent has no sense of what these parameters do or how they affect the listing, leaving the tool ambiguous.
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 a specific verb ('List') and resource ('Workspace Webhooks'), and adds scope with 'all webhooks for a workspace.' This distinguishes it from sibling webhook tools like create/update/delete workspace webhook route.
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 is given about when to use this tool versus alternatives, such as create/update/delete webhook route tools. There are no explicit exclusions, conditions, or usage context beyond restating the tool's basic function.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
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.