Skip to main content
Glama

Get download link

get_download
Read-only

Get a signed download link for the finished video (use when the video is ready and the user wants the file)

Use once get_lesson says the video is done. Returns a URL (valid 900 s) to the MP4, not the file itself: hand the link to the user or fetch it. variant=720 is the light copy every plan gets, variant=1080 is full quality and needs a paid plan.

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": {
      "id": "<id>"
    },
    "name": "get_download"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesid
variantNovariant1080

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description adds substantial context beyond them: the URL expires in 900 s, it is a link rather than the file, and 1080 requires a paid plan. These are exactly the behavioral details an agent needs before committing.

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?

Front-loaded with the action and the timing condition, and every clause carries information. Slightly dense with a mid-sentence parenthetical and multiple clauses, but no wasted text.

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

Completeness5/5

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

No output schema exists, yet the description covers the return value (a URL valid 900 s to an MP4), what the caller should do with it, and plan gating on the variant. Nothing needed to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% but the schema only lists bare enum values ('720', '1080'). The description gives real meaning: 720 is the light copy on every plan, 1080 is full quality requiring a paid plan — a crucial caveat since the schema defaults to 1080.

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 a signed download link for the finished video') and distinguishes itself from get_lesson by positioning that tool as the readiness check. An agent can tell immediately this returns a link, not the video.

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

Usage Guidelines5/5

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

Explicit timing condition ('use when the video is ready and the user wants the file') plus a named prerequisite ('once get_lesson says the video is done'). The alternative for status checking (get_lesson) is implied through that reference.

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.

Resources