Skip to main content
Glama
Sign In

FastSaver API

by io.fastsaver
OverviewDiscussionsAdmin

Fetch media from a post link

fetch_media
Read-only

Get direct download links and metadata for one public post, reel, story, video or pin from Instagram, TikTok, Pinterest, Facebook, X (Twitter), Rutube or Likee. Returns type, download_url, thumbnail_url, width, height, duration and caption; an album returns its files in items. Credits per call: Instagram stories and highlights 5, Instagram 1.5, TikTok 1.5, Pinterest 1.5, Facebook 1.5, X (Twitter) 1.5, Rutube 3, Likee 3. A failed call or an unsupported link costs 0.1.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe link as copied from the app or the browser.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing the returned field set, the album/items shape, and per-platform credit costs including a distinct 0.1 charge for failed or unsupported links. That cost asymmetry is exactly the kind of behavior an agent cannot get from structured fields.

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?

Front-loaded with the action and scope, then return shape, then credit economics in a single sentence. Every clause carries information — even the platform credit list is decision-relevant, not filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly supplies return fields and the album exception, and covers cost behavior including failures. What remains unstated is error surface for private or removed content beyond the 'public' qualifier, a minor gap for an open-world fetch tool.

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?

With a single parameter at 100% schema coverage, the baseline is 4, and the description modestly adds value by clarifying that the accepted input is a link to one public post from the listed apps. It doesn't add URL format rules beyond the schema's 'as copied from the app or the browser', but nothing is missing.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get direct download links and metadata for one public post, reel, story, video or pin') and enumerates the exact supported platforms, which implicitly separates it from the YouTube-specific siblings. An agent can tell what it does and what it scope-limits to without opening the schema.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'one public post' signals single-item, public-only use, and the unsupported-link credit note hints at failure behavior. However, there is no explicit routing guidance to alternatives such as youtube_download or list_supported_platforms, leaving the agent to infer when this tool is the right choice.

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

All FastSaver API 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