Skip to main content
Glama

lunara_subtitle_from_url

Start a persisted subtitle job from a URL you already host — no upload needed. Returns a job id; poll lunara_get_job every 15–30 s until status is "completed", then call lunara_get_srt. Prefer this over lunara_upload_video whenever the media is reachable by URL.

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_subtitle_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
audioUrlYesDirect HTTP(S) URL to the audio or video file. Must be downloadable by our server.
filenameNoDisplay name for the result. Defaults to the URL basename.
spokenLangNoWhat the speaker is speaking, e.g. yue-Hant-HK. Defaults to auto-detect.
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

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false; the description adds the async nature (persisted job, job id returned) and an explicit polling cadence, which is meaningful context not present in annotations. It does not explicitly warn that repeated calls create separate jobs (i.e., non-idempotency in practice) or discuss failure modes for unreachable URLs, leaving a small gap.

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?

Three short sentences, front-loaded with what the tool does, then the workflow, then the routing rule. Every clause carries information an agent needs; nothing is redundant.

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?

For a six-parameter async job-start tool with no output schema, the description supplies the missing return semantics (a job id) and the full polling/retrieval chain, plus the alternative-selection rule. An agent has everything needed to call it and handle the result correctly.

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%, so every parameter (audioUrl, filename, spokenLang, primaryLang, secondaryLang, secondaryLangs) is already documented, including the cost note on multi-language translation. The description adds nothing parameter-specific beyond the URL-hosted constraint, so the baseline of 3 applies.

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?

States a specific verb and resource ("Start a persisted subtitle job from a URL") and adds the key qualifier "you already host — no upload needed," which immediately separates it from upload-based siblings. An agent can identify the operation and its input mode without opening the schema.

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?

Explicitly routes the agent: "Prefer this over lunara_upload_video whenever the media is reachable by URL" names the alternative and the selecting condition. It also spells out the follow-up workflow (poll lunara_get_job every 15–30 s until "completed", then lunara_get_srt), so both entry and exit paths are documented.

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