Update Member. Updates attributes of a workspace member. Apart from the email identifier, all parameters will remain unchanged unless specified. This endpoint may only be called by workspace administrators.
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | |||
| account | No | ||
| is_locked | No | ||
| workspace_role | No | ||
| workspace_seat_type | 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 adds behavioral context beyond annotations by stating that 'all parameters will remain unchanged unless specified,' indicating partial-update semantics rather than full replacement. It also discloses the administrative authorization requirement, which the annotations do not cover. No contradiction with readOnlyHint=false, destructiveHint=false, or idempotentHint=false.
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 compact and front-loaded with the core purpose. The first sentence is somewhat redundant ('Update Member' vs the tool name), but the second and third sentences add genuinely useful information about partial updates and administrative access. No wasted words overall.
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 mutation tool with no output schema and five parameters, the description covers the essential update semantics and access restriction, but omits parameter-level guidance and any description of return behavior or effects. It is adequate for basic invocation but incomplete for nuanced use, especially around workspace_role versus workspace_seat_type.
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%, and the description does not explain any of the actual parameters beyond calling email an identifier. It does not clarify what account, is_locked, workspace_role, or workspace_seat_type do or how they relate to the partial-update behavior. This leaves the agent to infer semantics solely from parameter names and enums, which is insufficient.
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 action: 'Updates attributes of a workspace member.' It distinguishes this from sibling tools like elevenlabs_add_member and elevenlabs_remove_member by focusing on attribute updates rather than creation or removal. The admin-only note further clarifies the intended scope.
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 provides clear context: this is for updating existing workspace member attributes and is restricted to workspace administrators. It does not explicitly compare against alternatives like add_member or remove_member, but the admin-only constraint and update-specific language give adequate usage guidance.
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.