Skip to main content
Glama
Sign In

Fahi-Videos MCP Server

by io.github.khondokartowsif171
OverviewDiscussionsAdmin

fahi_extract_media_info

[100% FREE — Zero API Key Needed] Extract downloadable HD MP4 video and MP3 audio streams for YouTube (Videos/Shorts), Facebook (Videos/Reels/fb.watch), Instagram (Reels/Posts), and TikTok links.

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": {
      "url": "<url>"
    },
    "name": "fahi_extract_media_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic YouTube, Facebook, Instagram, or TikTok video/reel URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does add genuine behavioral context: no API key or payment is required, and the output is described as downloadable streams rather than a completed download. It omits whether the tool actually downloads a file or returns direct links, whether the public URL must be publicly accessible, failure behavior for private/geo-blocked content, and any rate limits or length limits.

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 that leads with the free/no-key qualifier and then delivers the verb, output formats, and supported platforms in that order. Nothing is redundant and nothing could be removed without losing information.

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 tool with no output schema, the description should clarify what an agent gets back (direct stream URLs? metadata? multiple resolutions?) and this is not stated. Platform coverage is well handled, but the return-value gap leaves the agent guessing about the next step.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description nonetheless adds meaning beyond the schema's generic "Public YouTube, Facebook, Instagram, or TikTok video/reel URL" by enumerating accepted URL forms (Shorts, Reels, fb.watch, Posts), telling the agent which link shapes are valid.

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?

States a specific verb ("Extract") and concrete resources ("downloadable HD MP4 video and MP3 audio streams") scoped to four named platforms, so an agent knows exactly what operation and output types to expect. It stops short of explicitly contrasting itself with the sibling generation/editing tools, which is why it is a 4 rather than a 5.

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, no statement of prerequisites, and no named alternative. An agent must infer from the platform list alone that this tool is the entry point for turning a social video URL into stream links before any downloading step.

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