Skip to main content
Glama

Add subtitles to video

add_subtitles_to_video

Adds automatically generated subtitles to a supplied video segment using a subtitle preset or custom text styling. Starts a background job that costs credits; returns a project id for wait_for_video_project. Before choosing settings, read get_account_info and the current parameter constraints. A listed model, resolution, duration or count is not necessarily available together or on this account. Preserve explicit requirements and all supplied inputs; explain a genuine block instead of submitting an incompatible request. Account balance alone does not prove a request is affordable. Use the named attachment fields first for ChatGPT files. Ask which file goes where if their roles are unclear. If a file fails, ask the user to attach it again and keep the requested settings.

Input Schema

NameRequiredDescriptionDefault
nameNoOptional project name for identifying this output. Omit to use the API's default project name.Auto Subtitle - dateTime
styleYesStyle of the subtitle. At least one of `.style.template` or `.style.custom_config` must be provided. * If only `.style.template` is provided, default values for the template will be used. * If both are provided, the fields in `.style.custom_config` will be used to overwrite the fields in `.style.template`. * If only `.style.custom_config` is provided, then all fields in `.style.custom_config` will be used. To use custom config only, the following `custom_config` params are required: * `.style.custom_config.font` * `.style.custom_config.text_color` * `.style.custom_config.vertical_position` * `.style.custom_config.horizontal_position`
videoNoAttach the video from ChatGPT for this input.
assetsNoProvide the assets for auto subtitle generator
end_secondsYesEnd time of your clip (seconds). Must be greater than start_seconds.
start_secondsYesStart time of your clip (seconds). Must be ≥ 0.

Output Schema

NameRequiredDescriptionDefault
idYesUnique ID of the video. Use it with the [Get video Project API](https://docs.magichour.ai/api-reference/video-projects/get-video-details) to fetch status and downloads.
credits_chargedYesThe amount of credits deducted from your account to generate the video. If the status is not 'complete', this value is an estimate and may be adjusted upon completion based on the actual FPS of the output video. If video generation fails, credits will be refunded, and this field will be updated to include the refund.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / anyOf
      Added value: +[
      +  {
      +    "required": [
      +      "video"
      +    ]
      +  },
      +  {
      +    "properties": {
      +      "assets": {
      +        "required": [
      +          "video_file_path"
      +        ]
      +      }
      +    },
      +    "required": [
      +      "assets"
      +    ]
      +  }
      +]
    • removedInput schema / properties / assets / required
      Removed value: -[
      -  "video_file_path"
      -]
    • addedInput schema / properties / video
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Attach the video from ChatGPT for this input.",
      +  "properties": {
      +    "download_url": {
      +      "description": "Exact HTTPS download URL supplied for the native ChatGPT attachment, including its signed query.",
      +      "title": "Download Url",
      +      "type": "string"
      +    },
      +    "file_id": {
      +      "description": "Native ChatGPT file identifier paired with download_url; not a local filesystem path.",
      +      "title": "File Id",
      +      "type": "string"
      +    },
      +    "file_name": {
      +      "default": "",
      +      "description": "Original attachment filename, when supplied by ChatGPT.",
      +      "title": "File Name",
      +      "type": "string"
      +    },
      +    "mime_type": {
      +      "default": "",
      +      "description": "Attachment MIME type, when supplied by ChatGPT.",
      +      "title": "Mime Type",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "download_url",
      +    "file_id"
      +  ],
      +  "title": "ChatGPTFile",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "start_seconds",
      -  "end_seconds",
      -  "assets",
      -  "style"
      -]New value: +[
      +  "start_seconds",
      +  "end_seconds",
      +  "style"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Give your video a custom name for easy identification."New value: +"Optional project name for identifying this output. Omit to use the API's default project name."
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, open-world, non-idempotent, non-destructive operation, so the bar is lower; the description still adds real value by disclosing that it starts a background job, consumes credits, and returns a project id for polling. It does not cover retry/duplicate-submission risk (relevant given idempotentHint=false) or what an incompatible request produces as an error, leaving a gap for a mutating, credit-spending call.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the async/credit disclosure are front-loaded and earn their place. However, the second half accumulates agent-directed instructions of varying relevance ('Account balance alone does not prove a request is affordable', 'explain a genuine block') that dilute the tool-specific signal and partially restate schema guidance about attachments.

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?

For a complex tool with nested style config, two file-input paths, and an output schema (so return values need no explanation), the description covers prerequisites, cost, async lifecycle, and file attaching. It leaves out duplicate-request/idempotency behavior and what happens to an existing project on failure, which are the only material gaps.

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 the baseline is 3; the description adds only framing-level meaning, notably that listed models, resolutions, durations, or counts may not be combinable or available on the account. It does not explain the video-vs-assets duality or the start/end segment semantics beyond what the schema already documents.

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 first sentence gives a specific verb, resource, and scope: automatically generated subtitles applied to a supplied video segment, via preset or custom styling. An agent can immediately tell this apart from siblings like translate_video or edit_video because the output artifact (subtitles burned in on a time segment) is named explicitly.

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?

It gives explicit preconditions (read get_account_info and current parameter constraints before choosing settings) and names the downstream step (wait_for_video_project with the returned project id). It also tells the agent what to do about unclear file roles and failed attachments. It stops short of naming when-not-to-use-this versus specific sibling tools, so it falls below a 5.

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.