Skip to main content
Glama

net-web-media

subtitle_time_shift_and_fix

Shift all SRT/VTT subtitle timestamps forward/backward by exact milliseconds and detect overlapping cues.

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_time_shift_and_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
shiftMsNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden and falls short: it doesn't say whether the shifted subtitles are returned as text, written back to filePath, or both; whether 'detect overlapping cues' merely reports overlaps or silently repairs them; or what happens to cues that would go negative. Mentioning that all timestamps are shifted is useful, but the mutating effect and its limits are not disclosed.

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

Conciseness4/5

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

A single compact sentence, front-loaded with the primary action before the secondary detection behavior. The trailing 'and detect overlapping cues' is efficient but slightly under-explained for a second capability.

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?

It covers the essential action and the two subtitle formats, which is enough to attempt a call, but for a no-annotation mutation tool with zero schema description coverage it omits return behavior, input precedence, and the meaning of 'fix'.

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 coverage is 0% across three parameters, so the description must compensate and only partly does: 'exact milliseconds' clarifies shiftMs units and implies that a negative value shifts backward. It says nothing about the text vs. filePath inputs, which one takes precedence, or that both are optional despite a required parameter count of zero.

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 and resource ('Shift all SRT/VTT subtitle timestamps') plus a secondary function ('detect overlapping cues'), so the core purpose is clear. What 'fix' in the tool name means is never explained, and no sibling such as subtitle_convert_srt_vtt is referenced to differentiate scope.

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

Usage Guidelines2/5

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

There is no when-to-use statement, no when-not-to-use, and no reference to the related subtitle_convert_srt_vtt tool. An agent must infer that this is for retiming existing subtitles rather than converting formats.

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