Skip to main content
Glama

lunara_start_subtitle_job

Run the full eight-layer subtitle pipeline on an audio or video URL you can already host. Produces a written-language track and a translated track. Prefer lunara_upload_video when the file is local.

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": {
      "audioUrl": "<audioUrl>"
    },
    "name": "lunara_start_subtitle_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioUrlYesA URL Lunara can download (public or pre-signed).
spokenLangNoWhat the speaker is speaking, e.g. yue-Hant-HK. Defaults to primaryLang.
primaryLangNoLanguage of the written track. Default yue-Hant.
secondaryLangNoLanguage of the translated track. Default en.
secondaryLangsNoTranslation languages to produce in the same job (max 16). Merged with secondaryLang. Each one costs a separate translation pass; the speech is transcribed once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / secondaryLangs
      Added value: +{
      +  "description": "Translation languages to produce in the same job (max 16). Merged with secondaryLang. Each one costs a separate translation pass; the speech is transcribed once.",
      +  "items": {
      +    "enum": [
      +      "zh-Hant",
      +      "zh-CN",
      +      "yue-Hant",
      +      "en",
      +      "ja",
      +      "ko",
      +      "es",
      +      "fr",
      +      "de",
      +      "it",
      +      "pt",
      +      "pt-BR",
      +      "nl",
      +      "sv",
      +      "da",
      +      "no",
      +      "fi",
      +      "pl",
      +      "cs",
      +      "sk",
      +      "hu",
      +      "ro",
      +      "hr",
      +      "sl",
      +      "et",
      +      "lv",
      +      "lt",
      +      "ru",
      +      "uk",
      +      "bg",
      +      "sr",
      +      "ar",
      +      "he",
      +      "fa",
      +      "tr",
      +      "hi",
      +      "th",
      +      "vi",
      +      "id",
      +      "ms",
      +      "tl",
      +      "el",
      +      "sw"
      +    ],
      +    "type": "string"
      +  },
      +  "maxItems": 16,
      +  "type": "array"
      +}
  2. Changed2 schema fields changed
    • changedInput schema / properties / primaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "zh-Hans",
      -  "yue-Hant",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de",
      -  "it",
      -  "pt",
      -  "pt-BR",
      -  "nl",
      -  "sv",
      -  "da",
      -  "no",
      -  "fi",
      -  "pl",
      -  "cs",
      -  "sk",
      -  "hu",
      -  "ro",
      -  "hr",
      -  "sl",
      -  "et",
      -  "lv",
      -  "lt",
      -  "ru",
      -  "uk",
      -  "bg",
      -  "sr",
      -  "ar",
      -  "he",
      -  "fa",
      -  "tr",
      -  "hi",
      -  "th",
      -  "vi",
      -  "id",
      -  "ms",
      -  "tl",
      -  "el",
      -  "sw"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-CN",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
    • changedInput schema / properties / secondaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "zh-Hans",
      -  "yue-Hant",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de",
      -  "it",
      -  "pt",
      -  "pt-BR",
      -  "nl",
      -  "sv",
      -  "da",
      -  "no",
      -  "fi",
      -  "pl",
      -  "cs",
      -  "sk",
      -  "hu",
      -  "ro",
      -  "hr",
      -  "sl",
      -  "et",
      -  "lv",
      -  "lt",
      -  "ru",
      -  "uk",
      -  "bg",
      -  "sr",
      -  "ar",
      -  "he",
      -  "fa",
      -  "tr",
      -  "hi",
      -  "th",
      -  "vi",
      -  "id",
      -  "ms",
      -  "tl",
      -  "el",
      -  "sw"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-CN",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / primaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "yue-Hant",
      -  "zh-CN",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-Hans",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
    • changedInput schema / properties / secondaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "yue-Hant",
      -  "zh-CN",
      -  "en",
      -  "ja",
      -  "ko",
      -  "es",
      -  "fr",
      -  "de"
      -]New value: +[
      +  "zh-Hant",
      +  "zh-Hans",
      +  "yue-Hant",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de",
      +  "it",
      +  "pt",
      +  "pt-BR",
      +  "nl",
      +  "sv",
      +  "da",
      +  "no",
      +  "fi",
      +  "pl",
      +  "cs",
      +  "sk",
      +  "hu",
      +  "ro",
      +  "hr",
      +  "sl",
      +  "et",
      +  "lv",
      +  "lt",
      +  "ru",
      +  "uk",
      +  "bg",
      +  "sr",
      +  "ar",
      +  "he",
      +  "fa",
      +  "tr",
      +  "hi",
      +  "th",
      +  "vi",
      +  "id",
      +  "ms",
      +  "tl",
      +  "el",
      +  "sw"
      +]
  4. Changed2 schema fields changed
    • changedInput schema / properties / primaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "yue-Hant",
      -  "zh-CN",
      -  "en",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "zh-Hant",
      +  "yue-Hant",
      +  "zh-CN",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de"
      +]
    • changedInput schema / properties / secondaryLang / enum
      Previous value: -[
      -  "zh-Hant",
      -  "yue-Hant",
      -  "zh-CN",
      -  "en",
      -  "ja",
      -  "ko"
      -]New value: +[
      +  "zh-Hant",
      +  "yue-Hant",
      +  "zh-CN",
      +  "en",
      +  "ja",
      +  "ko",
      +  "es",
      +  "fr",
      +  "de"
      +]
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already disclose non-read-only, open-world, non-idempotent, non-destructive behavior, so the description need only add context. It adds the pipeline shape and dual output tracks, but never says this is an asynchronous job that must be polled (with lunara_get_job) or mentions cost/duration tied to the eight layers, which an agent needs before calling.

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 short sentences, front-loaded with the operation and followed by the output and the routing rule; no filler. Slightly under-specified rather than over-long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter, open-world, non-idempotent pipeline job with no output schema, the definition omits what comes back (a job handle) and how to follow up. The schema is rich, so the remaining gap is mainly lifecycle guidance.

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 description coverage is 100%, including enum values and defaults, so the baseline is 3. The description adds only the implied constraint that the URL must be one Lunara can reach ('you can already host'), without clarifying language-parameter interactions that the schema already covers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('run the full eight-layer subtitle pipeline on an audio or video URL') and states the output ('a written-language track and a translated track'). It does not differentiate itself from the very similarly named sibling lunara_subtitle_from_url, which is the most likely source of misselection.

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?

Gives one explicit routing rule: 'Prefer lunara_upload_video when the file is local.' That covers the local-vs-remote branch well, but leaves the choice against lunara_subtitle_from_url (and the granular lunara_transcribe/lunara_translate siblings) entirely unaddressed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources