Fahi-Videos MCP Server

fahi_capcut_editor_blueprint

[100% FREE — Zero API Key Needed] Generate a complete CapCut Pro Video Studio timeline configuration (00:00 left-aligned clips, CSS mask clip-paths, In/Out/Combo animation transforms, HSL color grading, and .SRT captions).

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": "fahi_capcut_editor_blueprint"
  }
}

Input Schema

Name	Required	Description
`animIn`	No	Clip entry animation.
`animOut`	No	Clip exit animation.
`animCombo`	No	Clip combo animation.
`maskShape`	No	CapCut mask shape.
`aspectRatio`	No	Target video aspect ratio.
`durationSec`	No	Total timeline duration in seconds (default: 15).
`projectTitle`	No	Project title for the CapCut Video Editor.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It never says whether the tool only computes a config (no side effects) or writes/persists anything, nor what the response looks like — a raw JSON string, a file, or a download link. The 'FREE / no API key' bracket is marketing rather than behavioral disclosure.

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 dense sentence that front-loads the artifact being produced, with no redundant restatement. The leading '[100% FREE — Zero API Key Needed]' promotion does not help tool selection and slightly dilutes the front-loading.

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?

For a 7-parameter generator with no annotations and no output schema, the definition should state what is returned and whether anything is persisted or rendered. The description covers the what but leaves the return contract, side effects, and typical usage scenario unaddressed.

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 coverage is 100% with five enums and a documented default of 15 seconds, so the schema already carries parameter meaning. The description adds only a thematic gloss (masks, animations, grading, captions) and even references HSL color grading that has no corresponding parameter, so it adds little beyond structured data. Baseline 3 is correct.

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 plus a very specific artifact: a 'CapCut Pro Video Studio timeline configuration' with enumerated components (left-aligned clips, mask clip-paths, In/Out/Combo transforms, HSL grading, .SRT captions). This is far more precise than a restatement of the name, and it distinguishes the tool from generate-only siblings like fahi_generate_srt_subtitles. It stops short of naming a sibling or scenario, so a 5 is not warranted.

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 statement of when to use this versus fahi_build_ugc_storyboard or fahi_generate_srt_subtitles, and no prerequisites, constraints, or exclusions beyond the promotional 'no API key' claim. An agent must infer the use case entirely from the artifact name.

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 tools Inspect

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.