audiobook_mcp

Overview Schema Source Related Servers Discussions Admin

Loop a conversion job forward until it finishes or a time cap is hit

audiobook_run_until_done

Advance an audiobook conversion job in timed chunks until finished or the time cap is reached, returning progress. Call again with the same job ID to resume from where it stopped.

Instructions

Repeatedly advance a job in chunk_seconds increments, reporting progress, until either it finishes or max_total_seconds elapses -- whichever comes first. This is the convenient one-call way to drive a job; use audiobook_continue_conversion directly instead if you want fine-grained control over each chunk (e.g. to react to a warning partway through).

For a long book this may still return with "done": false if max_total_seconds wasn't enough -- just call it again with the same job_id to keep going; already-completed work is never redone.

Args: params (RunUntilDoneInput): - job_id (str): from audiobook_start_conversion. - chunk_seconds (float): size of each internal step (default 60). - max_total_seconds (float): overall cap for this call (default 1200s / 20 min).

Returns: str: JSON status object (same schema as audiobook_get_status) plus: - "elapsed_seconds" (float): how long this call actually ran. - "chunks_run" (int): how many internal chunks it took.

Error Handling: - Same as audiobook_continue_conversion. If a chunk raises partway through the loop, the loop stops immediately and the error is returned -- prior chunks in this call are already checkpointed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations only provide hints like readOnlyHint=false and idempotentHint=false. The description goes further by disclosing the chunked looping mechanism, stop conditions, checkpointing behavior, no-redo guarantee, and error-handling semantics. It adds substantial behavioral context beyond the annotations and does not contradict them.

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?

The description is detailed but every sentence earns its place: core behavior, usage guidance, parameter semantics, return value extension, and error handling are each covered in compact, well-organized sections. The most important behavioral facts are front-loaded.

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?

This is a stateful looping operation with non-trivial stopping conditions and error behavior. The description covers how to invoke it, what its bounds are, what the return value includes, how to resume, and how errors are handled. An agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the schema coverage being 0%, the description thoroughly explains each parameter: job_id's source, chunk_seconds as the internal step size, and max_total_seconds as the overall cap with a clear 'call again to keep going' semantic. This fully compensates for the lack of schema-level descriptions.

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 description states a specific verb and resource: 'Repeatedly advance a job... until it finishes or max_total_seconds elapses.' It also explicitly distinguishes this tool from audiobook_continue_conversion, giving an agent a clear basis for selection without reading schemas.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool (convenient one-call driving) and when to prefer the alternative (fine-grained control via audiobook_continue_conversion). It also tells the agent what to do if the job isn't done: call again with the same job_id, since completed work is never redone.

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

Deploy Server