ElevenLabs MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

search_voices

Read-only

Find existing voices in your ElevenLabs library by searching name, description, labels, or category. Sort results by creation date or name.

Instructions

Search for existing voices, a voice that has already been added to the user's ElevenLabs voice library.
Searches in name, description, labels and category.

Args:
    search: Search term to filter voices by. Searches in name, description, labels and category.
    sort: Which field to sort by. `created_at_unix` might not be available for older voices.
    sort_direction: Sort order, either ascending or descending.

Returns:
    List of voices that match the search criteria.

Input Schema

TableJSON Schema

Name	Required	Default
`sort`	No	name
`search`	No
`sort_direction`	No	desc

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.1Apr 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "McpVoice": {
+      "properties": {
+        "category": {
+          "title": "Category",
+          "type": "string"
+        },
+        "fine_tuning_status": {
+          "anyOf": [
+            {
+              "additionalProperties": true,
+              "type": "object"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Fine Tuning Status"
+        },
+        "id": {
+          "title": "Id",
+          "type": "string"
+        },
+        "name": {
+          "title": "Name",
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "category"
+      ],
+      "title": "McpVoice",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/McpVoice"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "search_voicesOutput",
+  "type": "object"
+}

Addedv1.0.0Jan 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so the description adds value by detailing search behavior (fields searched) and a caveat about sort field 'created_at_unix' possibly missing. This is sufficient behavioral disclosure beyond annotations.

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 concise and front-loaded with the purpose. However, it redundantly states 'Searches in name, description, labels and category' both in the main description and the search param docstring. Minor redundancy, but overall well-structured.

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?

The description covers search functionality and sorting, and an output schema exists for return values. However, it lacks information on pagination, result limits, case sensitivity, or matching behavior. Given the tool's simplicity and the openWorldHint, this is adequate but not fully complete.

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

Parameters4/5

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

With 0% schema coverage, the description compensates well by explaining each parameter: 'search' describes the search fields, 'sort' notes a potential issue with older voices, and 'sort_direction' clarifies order. This adds context that the schema alone does not provide.

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 tool searches for voices already added to the user's ElevenLabs voice library, specifying the verb 'search' and the resource 'voices in user's library'. It also lists searchable fields (name, description, labels, category), differentiating it from the sibling 'search_voice_library' which likely searches public voices.

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?

The description provides clear context: it searches the user's own voice library across multiple fields. While it doesn't explicitly state when not to use it or compare to alternatives, the scope is well-defined, and the sibling name 'search_voice_library' implies a different usage. Minor lack of explicit exclusions prevents a perfect score.

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