Skip to main content
Glama
Sign In
Sync MCP Server

Sync MCP Server

Official
by synchronicity-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

check a dialogue edit preview

dialogue-previews_get
Read-only

Polls an Edit Dialogue audio preview by id to return its status, hosted preview audio, retimed transcript, and slot details for progress checks or review.

Instructions

Read one Edit Dialogue audio preview by id, rejecting it if it was not made from the given source video. Returns status (PENDING or PROCESSING while running; COMPLETED, COMPLETED_PARTIAL or FAILED when done), previewAudioUrl (hosted WAV of the whole edited window), resultTranscript (words retimed to the preview audio), resultSlots (each edited region's outputStartMs and outputDurationMs in the preview, sourceStartMs and sourceDurationMs in the source), the submitted sourceTranscript and edits, voiceId, partialDetail and error. Poll it while running; never create another preview to check progress. COMPLETED_PARTIAL is playable but incomplete: partialDetail.failedSlots lists regions that may sound rough, and reason background_bed_missing means only the speech was kept; tell the user which applies rather than reporting the preview as fully done. On FAILED, EDIT_TOO_LONG carries spanText and wordIds for the replacement to shorten, while codes such as VOICE_BLOCKED and SOURCE_TOO_LONG will not succeed on retry. Once the user approves the audio, pass this id as dialogueEditId to dialogue-videos_estimate and dialogue-videos_create; to revise, call dialogue-previews_create with previousPreviewId. Not for rendered videos (generations_get).

Input Schema

NameRequiredDescriptionDefault
idYesThe id returned by dialogue-previews_create.
projectIdYesThe projectId used with dialogue-previews_create.
videoAssetIdYesThe videoAssetId used to create this preview (the copy's id if dialogue-transcriptions_create returned one). A preview made from a different source video is rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.4
    • changedInput schema / properties / id / description
      Previous value: -"Preview id from dialogue-previews_create."New value: +"The id returned by dialogue-previews_create."
    • changedInput schema / properties / projectId / description
      Previous value: -"Project the Edit Dialogue work belongs to, from projects_create."New value: +"The projectId used with dialogue-previews_create."
    • changedInput schema / properties / videoAssetId / description
      Previous value: -"Saved VIDEO asset being edited. Use the videoAssetId dialogue-transcriptions_create returned when it made a copy."New value: +"The videoAssetId used to create this preview (the copy's id if dialogue-transcriptions_create returned one). A preview made from a different source video is rejected."
  2. Changed3 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"Preview id from dialogue-previews_create."
    • addedInput schema / properties / projectId / description
      Added value: +"Project the Edit Dialogue work belongs to, from projects_create."
    • addedInput schema / properties / videoAssetId / description
      Added value: +"Saved VIDEO asset being edited. Use the videoAssetId dialogue-transcriptions_create returned when it made a copy."
  3. Addedv0.1.5

TDQS

A4.6/5.0
Behavior5/5

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

Although the annotations already declare this as a safe read-only operation, the description adds substantial behavioral context: status lifecycle values, partial-completion semantics, failure-code retry implications, and how to interpret background_bed_missing and EDIT_TOO_LONG. This is unusually rich and directly useful for handling the tool's output correctly.

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?

The description is long but dense and front-loaded: it states the core read action first, then status behavior, polling guidance, partial/failed handling, and downstream routing. The density is justified by the tool's stateful preview workflow, though a few clauses could be tightened.

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?

There is no output schema, so the description carries the full burden of explaining return values and states, which it does thoroughly: status values, previewAudioUrl, resultTranscript, resultSlots, sourceTranscript, edits, voiceId, partialDetail, and error. It also explains what to do in each terminal state, making the definition complete for this tool.

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 coverage is already 100%, and all three parameters are documented in the schema itself, including the rejection behavior for a mismatched videoAssetId. The description reinforces that the preview must come from the given source video and that the id comes from dialogue-previews_create, but it does not add much parameter meaning beyond the schema.

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 starts with a specific verb and resource: read one Edit Dialogue audio preview by id. It also explicitly distinguishes this from rendered-video retrieval by saying it is not for generations_get, so an agent can select it confidently.

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 gives explicit polling guidance while the preview runs and forbids creating another preview just to check progress. It also names the alternative workflows: pass the approved id to dialogue-videos_estimate and dialogue-videos_create, revise via dialogue-previews_create with previousPreviewId, and use generations_get for rendered videos.

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