ElevenLabs

elevenlabs_edit_pvc_voice_sample

Update Pvc Voice Sample. Update a PVC voice sample - apply noise removal, select speaker, change trim times or file name.

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": {
      "voice_id": "<voice_id>",
      "sample_id": "<sample_id>"
    },
    "name": "elevenlabs_edit_pvc_voice_sample"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`voice_id`	Yes
`file_name`	No
`sample_id`	Yes
`trim_end_time`	No
`trim_start_time`	No
`selected_speaker_ids`	No
`remove_background_noise`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description matches the annotations: readOnlyHint=false and destructiveHint=false, so it is consistent. It adds some behavioral context by specifying what can be changed, but it does not mention side effects, reversibility, permission requirements, or what happens to the sample after editing.

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, but the first sentence largely repeats the second. The redundancy is minor because the second sentence quickly adds the specific update dimensions.

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 8 parameters, no output schema, and 0% schema description coverage, this description is thin. It names the operation and some editable fields but does not explain the required voice_id/sample_id relationship, trim time format, how speaker IDs are selected, or any post-edit implications.

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

Parameters3/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. It gives plain-language meaning for several parameters: noise removal, speaker selection, trim times, and file name. However, it does not clarify trim time units, required identifiers, the account parameter, or the semantics of selected_speaker_ids beyond 'select speaker'.

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: 'Update a PVC voice sample' and names the supported modifications (noise removal, speaker selection, trim times, file name). This clearly distinguishes it from sibling tools like create_pvc_voice, delete_pvc_voice_sample, and get_pvc_sample_audio.

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 usage context is implied by 'Update' and the list of editable attributes, but there is no explicit guidance about when to choose this over alternatives, prerequisites, or cases where it should not be used.

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.