Skip to main content
Glama

Edit a dub's lines

edit_lines
DestructiveIdempotent

Changes the dubbed words, delivery style or voice instructions of up to 100 lines. Early access. The changed lines are voiced again in the background and the dub's files update when that is done (status "revoicing").

Instructions

Changes the dubbed words, delivery style or voice instructions of up to 100 lines. Early access. The changed lines are voiced again in the background and the dub's files update when that is done (status "revoicing"). This replaces what is there, so confirm the exact new wording with the person first.

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": {
      "dub_id": "<dub_id>",
      "lines": "<lines>"
    },
    "name": "edit_lines"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesYes
dub_idYesThe dub's id, such as dub_…

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (destructiveHint, openWorldHint, idempotentHint) the description discloses genuinely new behavior: editing is asynchronous, changed lines are re-voiced in the background with status "revoicing", and the dub's files update only when that finishes. It also reinforces the destructive semantics by saying the edit replaces what is there, so an agent knows the prior wording is lost.

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 purpose and ending with the safety warning; the standalone 'Early access' fragment carries real stability information rather than filler. No sentence is redundant.

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

Completeness4/5

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

For a destructive async mutation with no output schema, the description covers the important gaps: limited to 100 lines, background revoicing with status, and eventual file update. It leaves one real ambiguity unresolved — since text/delivery_style/voice_instructions are individually optional, it never says whether omitting a field preserves or clears the existing value.

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 50% at the top level, so the description partially compensates by naming the three editable attributes (words, delivery style, voice instructions), which map to text, delivery_style and voice_instructions. The 100-line mention merely restates maxItems, and nothing clarifies the optionality of text or what omitting it does, so it adds only moderate 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?

States a specific verb and resource (change dubbed words, delivery style, voice instructions) plus a concrete scope cap of 100 lines, which makes it easy to tell apart from read-only siblings like list_lines or get_dub. It stops short of naming any alternative tool, but the operation itself is unambiguous.

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 practical context for invocation: it is early access, it overwrites existing content, and the exact new wording should be confirmed with the person first. It does not state exclusions or point to any alternative tool for different edit needs, which keeps it below a 5.

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