Skip to main content
Glama

net-web-media

subtitle_convert_srt_vtt

Convert SubRip (.srt) to WebVTT (.vtt), plain transcript (.txt), or reverse VTT -> SRT with exact millisecond timestamp preservation.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "subtitle_convert_srt_vtt"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo
targetFormatNovtt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute one real behavioral fact: timestamps are preserved to the millisecond. It says nothing about invalid/malformed input handling, whether output is returned inline or written to disk, or whether the two input modes are mutually exclusive, which matters for a mutation-free but still side-effecting converter.

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?

A single sentence with the supported conversions front-loaded and no filler. Every clause (source format, target formats, reverse direction, timestamp fidelity) carries information.

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

Completeness2/5

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

No annotations, no output schema, and 0% parameter coverage leave significant gaps for a tool with two alternate input modes and a defaulted enum. The definition should state how text/filePath interact and what the return value looks like; as written an agent must guess before its first call.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not. It clarifies the targetFormat values (vtt, srt, txt, with .txt described as a plain transcript) but leaves the most consequential ambiguity untouched: when to supply 'text' versus 'filePath', and what happens if both or neither are given.

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?

The description names a specific verb (convert) and resource (SubRip subtitle files) and enumerates the supported format pairs: SRT->VTT, SRT->TXT, and VTT->SRT. It is unambiguous on its own, though it never distinguishes itself from the sibling subtitle_time_shift_and_fix, which an agent could plausibly confuse with a conversion task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the format list: an agent can infer 'use this when you have a .srt or .vtt and want another subtitle format.' There is no explicit when-to-use, no when-not-to-use, and no pointer to the time-shift sibling for tasks that alter rather than convert timestamps.

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