ofaudio-mcp

add_library_voice

Add a shared Voice Library voice to your account under a custom name, enabling later speech generation with that character. Note: consumes one custom-voice slot.

Instructions

Add a shared Voice Library voice to the account and save it under name.

Take public_owner_id + voice_id from search_voice_library. After this, generate_speech(voice="") uses that character. NOTE: consumes one custom-voice slot on the ElevenLabs account (tiers cap how many you can hold).

Returns: {"voice_id": , "name": ...} or {"error": ...}.

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_owner_id": "<public_owner_id>",
      "voice_id": "<voice_id>",
      "name": "<name>"
    },
    "name": "add_library_voice"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes
`voice_id`	Yes
`public_owner_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses a meaningful side effect ('consumes one custom-voice slot...') and describes return values. It doesn't cover potential failures or idempotency, but the disclosure is solid.

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

Conciseness5/5

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

The description is concise and well-structured: a clear opening sentence, a workflow note, a warning, and a returns section. Every sentence adds value without redundancy.

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

Completeness4/5

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

For a simple tool with three string params and no annotations, the description covers purpose, usage, side effects, and return format. It lacks explicit error handling details, but overall it is sufficiently complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by explaining that public_owner_id and voice_id come from search_voice_library, and that name is the saved name. All three parameters are semantically defined.

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 the action ('Add a shared Voice Library voice to the account and save it under `name`'), identifying the specific resource and outcome. It also references search_voice_library and generate_speech, distinguishing this from sibling tools.

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?

It provides explicit workflow context ('Take public_owner_id + voice_id from search_voice_library. After this, generate_speech(voice="<name>") uses that character'), which indicates when to use it. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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