Skip to main content
Glama

download_video

Idempotent

Retry a failed download for a video job or return the completed file path; no URL or path input is accepted and no charges apply.

Instructions

내려받지 못한(lost) 작업의 다운로드를 다시 시도하거나, 완료된 파일 경로를 돌려준다. 과금되지 않는다.

보통은 서버가 자동으로 내려받으므로 부를 필요가 없다. URL 이나 경로는 받지 않는다.

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": {
      "job_id": "<job_id>"
    },
    "name": "download_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations it discloses two non-obvious behavioral facts: the call is not billed, and normal operation does not require calling it at all. It also clarifies the retry semantics for 'lost' jobs, which the idempotentHint=true alone would not convey. It stops short of saying where the returned path points or whether the retry blocks.

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?

Two short blocks, front-loaded with the primary action before the caveat. Nothing is padded, though the negative constraint about URLs/paths is a little orphaned without parameter context around it.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. Still, for a two-parameter tool with zero schema documentation, the meaning of wait_seconds and the blocking/polling behavior are left entirely unexplained, which is a real gap for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the meaning of both parameters and largely does not. The line about not accepting URLs or paths indirectly tells the agent job_id is an identifier, but wait_seconds (default 30) is completely unexplained — there is no hint that it controls how long the retry waits before returning.

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 states a specific verb pair (retry a failed download / return the completed file path) tied to a specific resource (a video job's output file). It is clear enough to distinguish from siblings like get_video_status, but it never names those siblings or explicitly contrasts itself with them.

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

Usage Guidelines4/5

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

It gives an explicit when-not-to-use signal: the server normally downloads automatically, so calling is usually unnecessary. It also excludes a misuse mode by stating it does not accept URLs or paths. What is missing is a positive trigger condition tied to a sibling, e.g. after get_video_status reports a lost/failed download.

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