Skip to main content
Glama
marzvfx

lipdub-mcp

Official
by marzvfx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Wait for LipDub render to finish

lipdub_wait_for_render
Read-onlyIdempotent

Wait for a LipDub render to finish and retrieve its download link. Blocks until done or timeout, returning still_running when more time is needed—use after creating a render to avoid polling loops.

Instructions

Wait for a LipDub render to finish, then return its download link. Use this straight after lipdub_create_render instead of checking in a loop — it uses far less context.

This call blocks for up to max_wait_seconds (default 45, maximum 600) while tracking the render for you. A render takes several minutes for a short clip, and longer for longer videos, so expect to call this several times — that is normal and costs nothing.

If the render is still going when the wait is up, this returns normally with still_running set to true. That is NOT an error and NOT a failure — the render is fine and is still going. When it happens: tell the user it is still in progress, give them the render_id so they can come back to it, and call this tool again to keep waiting.

Waiting and status checks are free and never rate-limited.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
render_idYesThe render_id from lipdub_create_render.
max_wait_secondsNoHow long to wait before returning. Returning early with still_running set to true is normal, not a failure. The default of 45 stays under the 60-second request timeout most MCP clients use; only raise it if your client is configured to wait longer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / max_wait_seconds / default
      Previous value: -240New value: +45
    • changedInput schema / properties / max_wait_seconds / description
      Previous value: -"How long to wait before returning. Returning early with still_running set to true is normal, not a failure."New value: +"How long to wait before returning. Returning early with still_running set to true is normal, not a failure. The default of 45 stays under the 60-second request timeout most MCP clients use; only raise it if your client is configured to wait longer."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, but the description adds critical behavioral detail beyond these: the blocking nature, the max_wait_seconds cap, the normal return with still_running, and the explicit statement that it is not an error. No contradiction with annotations.

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 efficiently organized: purpose first, then usage, then behavior, then user guidance. Every sentence earns its place—no fluff. It front-loads the core purpose and the key differentiator, and the length is appropriate for the complexity of the tool.

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?

Despite lacking an output schema, the description fully covers what an agent needs: how to call it, what to expect (including partial results), how to handle still_running, and cost/rate-limit implications. It leaves no gaps for correct invocation and follow-up.

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 100% (both parameters documented). The description adds context beyond the schema, such as explaining that renders take several minutes and it's normal to call repeatedly, which informs how to set max_wait_seconds. However, the schema already covers the key semantics of max_wait_seconds and still_running, so the description's extra value is limited but present.

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 opens with a precise verb-resource pair: 'Wait for a LipDub render to finish, then return its download link.' It explicitly differentiates from alternatives by stating to use it 'straight after lipdub_create_render instead of checking in a loop,' making the tool's purpose unambiguous and distinct from siblings.

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?

The description gives explicit when-to-use guidance: 'Use this straight after lipdub_create_render instead of checking in a loop.' It also instructs what to do when still_running is true: tell the user, provide the render_id, and call again. It even notes that repeated calls are normal and free, covering both timing and cost expectations.

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

Deploy Server

Other Tools