ElevenLabs

elevenlabs_add_sharing_voice

Add Shared Voice. Add a shared voice to your collection of voices.

Bulk support: accepts public_user_ids, voice_ids for batched execution.

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": {
      "public_user_id": "<public_user_id>",
      "voice_id": "<voice_id>",
      "new_name": "<new_name>"
    },
    "name": "elevenlabs_add_sharing_voice"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`new_name`	Yes
`voice_id`	Yes
`voice_ids`	No
`bookmarked`	No
`public_user_id`	Yes
`public_user_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already communicate that this is a write operation and not destructive. The description adds some behavioral context by stating the voice is added to 'your collection' and mentioning batched execution via plural parameters, but it does not disclose naming-conflict behavior, permissions, or reversibility.

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 short and front-loaded, with the core purpose in the first sentence and the bulk capability in the final sentence. The only minor issue is that 'Add Shared Voice' redundantly repeats the tool name, but overall it is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, no output schema, and no parameter descriptions, this description is too sparse. It does not explain required versus optional usage, batch semantics in detail, account targeting, or expected outcomes, making it incomplete for reliable invocation.

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?

Schema description coverage is 0%, so the description must compensate, but it only mentions public_user_ids and voice_ids for bulk support. It fails to explain required fields like new_name, or optional ones like account and bookmarked, and does not clarify the relationship between singular and plural 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 uses a specific verb and resource: 'Add a shared voice to your collection of voices.' This clearly distinguishes the action from sibling tools like elevenlabs_create_voice, which creates a new voice, while this tool imports an existing shared voice.

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

Usage Guidelines3/5

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

The description implies the usage context—adding shared voices to a personal collection—and notes bulk execution support. However, it gives no explicit guidance on when to prefer this tool over alternatives such as create_voice, nor any exclusions or prerequisites.

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

All ElevenLabs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.