Podcast MCP

Overview Schema Source Related Servers Discussions Admin

speaker_enroll_tool

Enroll speaker voiceprints from an audio segment, a full track, or every media-backed track to identify speakers in podcast projects.

Instructions

Enroll voiceprints from a segment, a whole track, or every media-backed track.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "speaker_enroll_tool"
  }
}

Input Schema

Name	Required	Description	Default
`end_sec`	No
`track_id`	No
`start_sec`	No
`speaker_id`	No
`project_path`	No
`home_track_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Oct 19, 2026
- addedInput schema / properties / project_path / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / project_path / default
```
Added value: +null
```
- removedInput schema / properties / project_path / type
```
Removed value: -"string"
```
- removedInput schema / required
```
Removed value: -[
-  "project_path"
-]
```
First observedv0.1.0Sep 20, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description carries the full burden and only states the action. It omits whether enrollment mutates existing speaker profiles, what happens on conflict or duplicate speaker_id, permission requirements, and whether the operation is reversible.

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?

A single front-loaded sentence with no filler, moving directly to the action and scope. Efficient, though it trades away detail that would have been useful.

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?

An output schema exists so return values needn't be described. However, for a six-parameter mutation tool with zero schema descriptions and no annotations, the description is far too thin to call it correctly.

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 coverage is 0% across six parameters, so the description must compensate. It hints at the three modes (segment via start/end, whole track via track_id, all tracks via home_track_id) but leaves speaker_id and project_path undefined and adds no format or meaning.

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?

Specific verb (enroll) plus resource (voiceprints) and three scopes, which distinguishes it from siblings like speaker_score_tool or speaker_profiles_tool. The action is clear, though it doesn't explicitly name a sibling it contrasts with.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. There is no routing to alternatives such as speaker_attribute_tool, speaker_label_tool, or speaker_profiles_tool, so an agent must guess which speaker tool applies.

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

Deploy Server