Skip to main content
Glama

List a dub's lines

list_lines
Read-only

A finished dub's lines by number: timing in milliseconds, speaker, original and dubbed words, and delivery notes. Early access. Returns 100 lines at a time; use offset for more. Line numbers are what edit_lines and ask_reedapt refer to.

Instructions

A finished dub's lines by number: timing in milliseconds, speaker, original and dubbed words, and delivery notes. Early access. Returns 100 lines at a time; use offset for more. Line numbers are what edit_lines and ask_reedapt refer to.

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>"
    },
    "name": "list_lines"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations declare this to be a read-only, open-world operation. Beyond that, the description discloses the page size of 100 lines, the unit of timing (milliseconds), the presence of delivery notes, and an 'early access' availability caveat. It does not say how to tell whether more lines remain, however.

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?

Three dense sentences with no filler, and the important return payload is stated first. The opening fragment ('A finished dub's lines by number') is slightly compressed, but every sentence earns its place.

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 2-parameter list tool with no output schema, the description covers return fields, page size, and pagination behavior. It is nearly complete that only the semantics of a further 100 lines, such as a total count or end-of-list signal, are left unstated.

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 schema already defines dub_id, but it leaves offset without a description. The description compensates by explaining that each page returns 100 lines and that offset moves to the next page. It adds genuine meaning for the one undocumented parameter.

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 definition states a specific verb-plus-resource ('A finished dub's lines by number') and enumerates what each line contains: millisecond timing, speaker, original and dubbed words, and delivery notes. It is clearly distinguishable from list_dubs and is explicitly linked to edit_lines and ask_reedapt through the line-number concept.

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 phrase 'A finished dub's lines' signals the prerequisite that the dub must be complete, and 'use offset for more' gives concrete pagination guidance. It also states that line numbers are the identifiers used by edit_lines and ask_reedapt, which tells an agent how to chain calls. It stops short of explicitly saying when not to use this tool.

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