aidemo

Overview Schema Source Related Servers Discussions Admin

captions

Transcribe narration.mp3 into word-timed captions; returns a jobId for immediate polling via job_status. Rejects if another job is running to avoid concurrency.

Instructions

Transcribe narration.mp3 to captions with word timing. Returns a jobId immediately — poll job_status. Rejects if another job is running.

Input Schema

TableJSON Schema

Name	Required	Description
`dir`	Yes	demo project directory — pass an absolute path
`lang`	No	render a language variant from scene.narrations[<code>] over the shared take (artifacts namespaced: audio/<code>/, captions.<code>.*, output/final-demo.<code>.mp4). Omit for the default single-language render.
`params`	No	storyboard template params (name → value); each must be declared in the storyboard's params block. Substitutes {{name}} across all stages.
`offline`	No	approximate captions from the script — no network/STT
`alignScript`	No	use script spelling and punctuation with STT word timing

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes
`jobId`	Yes
`status`	Yes
`demoDir`	Yes	resolved absolute demo directory
`logFile`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.15.2Sep 25, 2026

addedInput schema / properties / alignScript

Added value: +{
+  "description": "use script spelling and punctuation with STT word timing",
+  "type": "boolean"
+}

First observedv0.9.0Sep 8, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the burden of behavioral disclosure and covers the most decision-relevant traits: the call is asynchronous, returns immediately, requires polling via job_status, and rejects concurrent jobs. It does not disclose filesystem effects or network behavior, but the core operational behavior is transparent.

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 two tight sentences with no filler: the first states the core operation and the second gives the async protocol and concurrency guardrail. It is front-loaded and 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?

Given the async workflow, concurrency constraint, and a clear pointer to job_status, the description covers the essential call-and-follow-up pattern. Combined with full schema coverage and an output schema, an agent has enough context to invoke and monitor the job, though explicit sibling routing would make it fully complete.

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?

All five parameters are already documented in the schema with 100% coverage, including dir, lang, params, offline, and alignScript, so the description does not need to restate them. The description adds no parameter-specific meaning beyond what the schema already provides, matching the baseline for full schema coverage.

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 names a specific source (narration.mp3), deliverable (captions), and property (word timing), and immediately clarifies the async contract by mentioning the returned jobId and job_status. This is specific enough to distinguish the tool from siblings like job_status or render even without an explicit comparison.

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

Usage Guidelines3/5

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

It implies a clear usage pattern: call this to create a captioning job, poll job_status for completion, and avoid launching while another job is running. However, it does not explicitly name alternatives or state when to prefer this tool over the many siblings, so the guidance is useful but incomplete.

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

Deploy Server