VoiceLabs

List voice profiles

list_voice_profiles

Read-onlyIdempotent

List the user's VoiceLabs voice profiles — both cloned voices and presets — with language, engine, and usage counts. Read-only. A brand-new account has none yet: an empty list comes back with an emptyState explaining how the user creates their first voice, which is what to relay instead of reporting that the tool failed.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`total`	Yes
`profiles`	Yes
`emptyState`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026
- removedOutput schema / properties / profiles / items / properties / default_engine / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / profiles / items / properties / default_engine / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / profiles / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / profiles / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the 'Read-only' sentence is redundant. However, the description adds genuinely new behavior: brand-new accounts return an empty list with an `emptyState` payload and how the agent should interpret it — context not present in any structured field.

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?

Three tight sentences: purpose first, safety second, edge-case handling last. Every sentence carries information the agent would otherwise have to discover at runtime.

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

Completeness5/5

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

An output schema exists, so return-shape documentation is not required, yet the description still surfaces the one non-obvious return case (empty account with `emptyState`). For a zero-parameter read tool this leaves nothing an agent needs unresolved.

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?

The tool takes zero parameters, so there is no parameter semantics to document; baseline 4 applies. The description correctly avoids inventing any filtering options the schema does not support.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the user's VoiceLabs voice profiles') and clarifies scope by naming both content kinds (cloned voices and presets) plus the fields returned. It does not explicitly route the agent away from the closely named sibling clone_voice_profile/ensure_voice_profile, so it falls just short of full sibling differentiation.

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?

Gives clear context for invocation and, unusually, guidance on handling the empty result ('relay the emptyState instead of reporting that the tool failed'). It lacks explicit when-not-to-use or named-alternative routing, but no ambiguity about the tool's role remains.

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

All VoiceLabs 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.

Resources

Need Help?