Skip to main content
Glama

Export subtitles

export_subtitles
Read-only

Caption segments as an SRT or WebVTT file body, for platforms that take separate subtitle files.

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": {
      "segments": "<segments>"
    },
    "name": "export_subtitles"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNosrt
segmentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With readOnlyHint=true already declared, the safety profile is covered and the description is consistent with it — this is a pure transformation. The description adds real value by saying the result is a file body rather than a file path or written asset, which changes how the caller must handle the return. It does not mention the 400-segment cap, handling of empty or malformed segments, or validation behavior, leaving behavioral gaps the annotations cannot fill.

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 front-loaded sentence with no boilerplate, no restatement of the title, and no filler. The output formats and the intended consumer appear before any subordinate clause, so the agent gets the essentials immediately.

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

Completeness3/5

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

The tool is simple — two parameters, one read-only transformation, no output schema — and the description correctly signals the return is a serialized body rather than a saved asset. Still missing for a formatting tool are timestamp units, the segment-count ceiling, and what happens with zero valid segments. Adequate, but not complete for an agent wiring this into a delivery pipeline.

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 both parameters, so the description carries full burden and only partially discharges it. It does clarify that 'format' means SRT vs. WebVTT and that 'segments' are caption segments, but it never states the units of start/end (seconds vs. milliseconds) or their base, which is the single highest-risk ambiguity for this tool. The nested segment fields are documented nowhere.

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 states a recognizable transformation: caption segments rendered out as either an SRT or WebVTT file body. It names both output formats and the artifact type (file body, not a file), which no sibling tool does. The phrasing is elliptical — no explicit verb like 'convert' or 'export' appears beyond the name — but the effect is unambiguous.

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?

'For platforms that take separate subtitle files' implies the when-to-use condition (external delivery vs. burned-in rendering) but names no alternative tool or exclusion. The agent must infer that in-project caption styling would go through a sibling such as list_caption_styles. Usage is implied, not stated.

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