Skip to main content
Glama

dubbing_assign_speakers

Idempotent

Assign speaker names to specific caption segments or ranges so dubbing uses the correct voice per speaker, especially when captions lack speaker markers.

Instructions

Set who speaks each segment. assignments maps a segment id ('7'), an inclusive range ('7-12') or '*' (all) to a speaker name, e.g. {'1-4': 'Anna', '5': 'Ben'}. Use when captions had no speaker markers.

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": {
      "project_id": "<project_id>",
      "assignments": "<assignments>"
    },
    "name": "dubbing_assign_speakers"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
assignmentsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare mutation (readOnlyHint=false), idempotency, and non-destructiveness, so the safety profile is covered. The description adds the important detail that keys can be individual ids, ranges, or '*', but does not say whether existing assignments are overwritten, what happens with invalid segment ids or unknown speaker names, or whether the project must be in a particular state. Those are real gaps for a mutation tool, though the annotation coverage lowers the burden.

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 short sentences, front-loaded with the action, followed by the format spec and the usage condition. The example earns its space by disambiguating the range and single-id forms.

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?

An output schema exists, so return values needn't be described. However, for a mutation that rewrites segment metadata, the definition omits overwrite behavior, validation/error behavior, and any ordering or prerequisite constraints, leaving an agent without a full behavioral picture.

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?

Schema coverage is 0% and `assignments` is an untyped additionalProperties map, so the description does the heavy lifting by explaining key formats ('7', '7-12', '*'), value meaning (speaker name), and giving a worked example. Only `project_id` is left implicit, which is acceptable for an obvious identifier.

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?

A specific verb plus resource: 'Set who speaks each segment.' It immediately conveys the operation is speaker-to-segment assignment, which is distinct from voice selection or translation siblings. The concrete assignment syntax removes any ambiguity about what is being set.

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?

'Use when captions had no speaker markers' gives a clear triggering condition. It does not name exclusions or an alternative (e.g., how this differs from setting a voice), but the positive guidance is strong enough for correct selection.

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