Skip to main content
Glama
Sign In

Fahi-Videos MCP Server

by io.github.khondokartowsif171
OverviewDiscussionsAdmin

fahi_generate_srt_subtitles

[100% FREE — Zero API Key Needed] Generate industry-standard SubRip (.srt) subtitle file content and CapCut HH:MM:SS:FF (30fps) timecodes from a list of scenes.

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": {
      "scenes": "<scenes>"
    },
    "name": "fahi_generate_srt_subtitles"
  }
}

Input Schema

NameRequiredDescriptionDefault
scenesYesOrdered list of scenes with start/end times and scripts.
bilingualNoInclude English title/translation line under each Bengali subtitle.

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 behavioral burden. It usefully discloses the output formats (SubRip SRT text plus 30fps CapCut timecodes) and that no API key is required. It does not disclose how the result is returned (inline string vs. file), whether output is validated, or any limits on scene count or duration.

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?

It is a single well-formed sentence with the key output formats front-loaded. The bracketed '[100% FREE — Zero API Key Needed]' is promotional framing that consumes attention without helping tool selection, though the rest is efficient.

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 two-parameter generator with a fully described schema and no output schema, the description covers inputs and output formats reasonably. It stops short of explaining the return shape (e.g., a string field containing the SRT and a separate timecode list) or error behavior, which an agent invoking it would want to know.

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?

Schema description coverage is 100%, so both parameters and the nested scene fields are already documented in the schema. The description adds nothing about the scenes array or the bilingual flag, so the baseline of 3 applies.

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: generating SubRip (.srt) subtitle content and CapCut HH:MM:SS:FF (30fps) timecodes from a list of scenes. That is concrete and unambiguous. It does not distinguish itself from any sibling (e.g., fahi_capcut_editor_blueprint or fahi_translate_and_adapt_scene), though the siblings appear functionally distinct.

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 alternatives are referenced. The only usage signal is implied by 'from a list of scenes'. Nothing tells the agent how this differs from the CapCut blueprint or translation tools in a multi-step workflow.

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

All Fahi-Videos MCP Server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources