Skip to main content
Glama

Download clip URL

download_clip
Read-only

Retrieves the verified GitHub Releases MP4 URL for a specified clip ID, letting AI agents obtain a direct download link for a catalog clip without handling raw bytes.

Instructions

Return verified GitHub Releases MP4 URL, not bytes.

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": {
      "clip_id": "<clip_id>"
    },
    "name": "download_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_idYes

Output Schema

NameRequiredDescriptionDefault
urlYes
clip_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and network profile are covered structurally. The description adds the useful fact that the result is a verified URL rather than file content, but says nothing about URL lifetime, verification cost, or what happens when no verified asset exists.

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?

A single short sentence with the key distinction ('URL, not bytes') front-loaded and no filler. It is efficient, though its extreme brevity borders on under-specification rather than tight writing.

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 no explanation, and annotations cover the safety profile. For a one-parameter read tool this is close to adequate, but it omits whether the URL is time-limited or requires auth and how failures surface, which matters for a download-oriented tool.

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?

There is only one parameter, clip_id, whose meaning is self-evident from its name and whose format is enforced by the schema pattern ^clip-\d{6}$. Schema description coverage is 0%, so the description could have explained the ID source, but the low parameter count keeps this near the baseline for simple tools.

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 names a specific resource (verified GitHub Releases MP4 URL) and clarifies the return type by contrast ('not bytes'), which lets an agent distinguish this from a metadata-fetch sibling like get_clip. The verb 'Return' is weaker than a precise action verb, but the resource and payload type are unambiguous.

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 'not bytes' phrasing implies when to prefer this tool (when a URL is wanted rather than content), but no sibling is named and no preconditions or exclusions are stated. An agent must infer routing from the sibling list rather than from the definition.

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