Skip to main content
Glama

Subtitle transcript export

bpj_subtitle_transcript_export
Read-onlyIdempotent

Remove timing, numbering and simple tags and export one transcript line per cue.

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": {
      "text": "<text>"
    },
    "name": "bpj_subtitle_transcript_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully adds what is stripped ('timing, numbering and simple tags') and the output shape ('one transcript line per cue'), but leaves 'simple tags' undefined and says nothing about how malformed or oversized input (maxLength 6000) is handled.

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, front-loaded with the transformation and ending with the output contract. No filler, no restatement of the tool name.

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?

For a one-parameter, no-output-schema, read-only tool this is close to sufficient, but two things an agent would want are missing: the expected subtitle input format and any note on length limits or behavior for input without cues. The transformation is described; the input contract is not.

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?

Only one parameter ('text') exists and schema coverage is 0%, so the description has to carry the meaning. It implies the input is raw subtitle content with cues, but never states the format (SRT/VTT?), the 6000-character limit, or whether multi-cue input is expected. Adequate, but it adds little concrete parameter guidance.

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 concrete transformation: strip timing, numbering and simple tags, then emit one transcript line per cue. That is a clear verb-plus-resource statement an agent can match against a subtitle-to-transcript task. It does not explicitly distinguish itself from the sibling export tools (e.g. markdown code block or blockquote export), but the resource is specific enough to separate it.

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 or when-not-to-use guidance, and no mention of what input this expects versus the other export or subtitle-analysis siblings. The agent must infer from the name alone that this is the plain-text transcript path rather than a markdown/XLIFF/TMX export.

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.