Skip to main content
Glama

subtitleDynamic

Generate subtitles for videos by transcribing audio automatically, or use provided text for precise captions. Customize font, position, and color to create subtitled videos.

Instructions

根据输入的视频地址,给视频添加字幕。如果原视频没有字幕,本接口可以自动识别视频中音频文字内容(无需调用其他接口提取视频中的文字内容),并将输出添加到视频上,形成带字幕的视频。 如果用户同时输入了字幕文本,以提供的文本作为参考,从而提升字幕文本的准确性,形成带字幕的视频。 字幕支持设置字体与位置等。支持传入text文本。 返回的内容是一个JSON结构,其中 taskID 代表任务查询id,traceId 任务跟踪id 注意:只需要返回接口内容,无需主动调用任务查询接口

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNo 字幕文本(可选、非必填)
marginVNo垂直边距(可选、非必填)
fontSizeNo字体大小(可选、非必填)
videoUrlYes需要转换为字幕的视频URL
isFontAutoNo是否自动调整字体大小,1自适应,0不自适应(可选、非必填)
isFontBoldNo是否加粗,1为加粗,0为不加粗,1自适应,0不自适应(可选、非必填)
selectFontNo选择字体编码,从1开始(可选、非必填)
textBgColorNo字幕背景颜色(可选、非必填)
primaryColorNo字体颜色(可选、非必填)
textStrokeColorNo描边颜色(可选、非必填)
textStrokeWidthNo描边宽度(可选、非必填)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.16

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden. It discloses automatic audio-to-subtitle recognition, the returned JSON structure with taskID and traceId, and instructs the agent not to call the task query interface. It does not explicitly state that processing is asynchronous, but the task IDs strongly imply it.

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 description is reasonably brief and front-loads the main purpose, but it contains redundancy: '形成带字幕的视频' appears twice, and the support for text input is restated after being implied earlier. A tighter structure would improve clarity.

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 tool has 11 parameters and no output schema, the description does a solid job by naming the return fields and instructing the agent not to follow up with the query interface. It does not fully describe async completion behavior or style parameter constraints, but the schema covers the parameter-level details.

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 11 parameters already have schema descriptions, so the baseline is 3. The description adds useful functional context, such as text being a reference to improve accuracy and that font/position settings are supported, but it does not clarify formats, units, or allowed values beyond what the schema already provides.

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 clearly states the core function: add subtitles to a video given a video URL. It also distinguishes itself from sibling tools by explicitly saying no other API is needed to extract speech from the audio when the original video has no subtitles.

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 gives concrete conditions for the two main usage modes: auto speech recognition when no subtitles exist, and using user-provided text as a reference when it is supplied. It also warns not to call an external text-extraction interface, though it does not name alternatives explicitly.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Runninghcm/MathMind-MCP-SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server