Skip to main content
Glama

Translate video

translate_video

Translates speech in a supplied video segment into a supported target language. 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.Video Translator - dateTime
videoNoAttach the video from ChatGPT for this input.
assetsNoSource video for the translation job.
resolutionNoOutput video resolution. Defaults to 480p. 720p and 1080p require a paid plan.
end_secondsYesEnd time of your clip (seconds). Must be greater than start_seconds. The clip must be 1-30 seconds long.
start_secondsNoStart time of your clip (seconds). Must be ≥ 0.
target_languageYesLanguage to translate the video's speech into.

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: -[
      -  "end_seconds",
      -  "target_language",
      -  "assets"
      -]New value: +[
      +  "end_seconds",
      +  "target_language"
      +]
  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

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses that this starts a background job, consumes credits, and returns a project id rather than a finished file. It also warns that listed enum values may not be available together or on the account, and that balance alone does not prove affordability — meaningful operational context. It does not address failure/refund behavior or turnaround time.

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 get_account_info/wait_for_video_project routing are front-loaded, which is good. However, the tail of the description drifts into generic policy boilerplate ("Preserve explicit requirements and all supplied inputs", "Ask which file goes where if their roles are unclear", "If a file fails, ask the user to attach it again") that is only loosely tied to invoking this specific tool.

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 7-parameter, nested-object, async job tool with an output schema, the description covers the essentials: what it produces, that it is asynchronous and credit-consuming, that account/plan gating applies, and how the two file-input shapes differ. Return-value details are correctly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline would be 3; the description earns above that by explaining that listed resolution/duration/count values are not necessarily combinable or available on the account, which is a constraint the schema's enums cannot express. It also directs the agent to the named attachment fields (video vs assets.video_file_path) first for ChatGPT files, adding disambiguation between the two input paths.

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?

"Translates speech in a supplied video segment into a supported target language" gives a specific verb (translate), resource (video speech), and scope (segment), which is enough to distinguish it from siblings like add_subtitles_to_video or edit_video. It stops short of naming the closest alternatives explicitly, so differentiation still requires some inference.

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?

The description routes the agent well: read get_account_info and current parameter constraints before choosing settings, and hand the returned project id to wait_for_video_project. It states the preconditions for a valid request but does not contrast this tool with adjacent video-editing siblings that could also accept a clip.

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.