Skip to main content
Glama

Save videos to my library

save_videos
Idempotent

Adds YouTube, Instagram or TikTok video links to the user's SavedThat library, where each one is transcribed and becomes searchable within a few minutes. Takes up to 25 links per call, counted against the same monthly save quota as saving in the app. Returns one result per link: saved, already_saved, invalid_url (not a supported video link), too_long (longer than the plan allows), limit_reached (the plan's save or library limit is used up; later links are not_attempted), or failed.

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": {
      "urls": "<urls>"
    },
    "name": "save_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesVideo links, for example https://www.instagram.com/reel/<id>/, a YouTube watch or Shorts link, or a TikTok video link.

Output Schema

NameRequiredDescriptionDefault
savedYes
resultsYes
not_savedYes
library_urlNo
already_savedYes
limit_reachedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a non-read-only, idempotent, non-destructive write; the description adds real value beyond them by disclosing asynchronous transcription and searchability 'within a few minutes', quota consumption, and per-link outcome states including already_saved and limit_reached. The only overlap is restating outcome codes that the output schema already enumerates.

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?

One dense paragraph, front-loaded with what the tool does and the supported sources before limits and outcomes. The trailing enumeration of six result codes is long but each code carries distinct information, so little is wasted.

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?

For a single-parameter write tool with annotations and an output schema, this covers batch size, quota accounting, processing latency, and failure modes. The result-code list duplicates the output schema rather than filling a genuine gap, which is the only shortfall.

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% and the single parameter already carries examples and maxItems=25, so the description is largely restating structured data. It adds only the framing that the count is 'per call' and drawn from a monthly quota; baseline 3 is appropriate.

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 ('Adds ... video links to the user's SavedThat library') plus the exact supported sources (YouTube, Instagram, TikTok). That is enough to separate it from search_my_library, list_my_saves, and get_my_queue without opening a 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?

The description gives useful operating context (up to 25 links per call, quota shared with in-app saves) but never says when to choose this tool over a sibling or when not to use it. Usage is inferable from the name and the write semantics rather than stated.

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.