Skip to main content
Glama

Get a link to upload a video

get_video_upload_link

Create a one-time link for sending a video file (MP4, MOV or M4V) to Tuney for scoring.

    Use this when the video is a local file, for example one the user attached or one in the
    working directory. Send the file with the curl command in `example` (HTTP PUT of the raw
    file); the response contains the video_id to pass to score_video. If the video is already
    online, use import_video with its link instead.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_video_upload_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
filenameNovideo.mp4

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare openWorldHint, non-idempotent, non-read-only and non-destructive, so the description's job is to add mechanics — and it does: the link is one-time, the file is sent via an HTTP PUT of the raw body using the curl command in `example`, and the response carries a video_id. It omits link expiry and any file-size or auth constraints, which would matter for an open-world upload endpoint.

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?

Three short sentences, front-loaded with the action and followed by the trigger condition and the alternative. The only wrinkle is the slightly indirect reference to the curl command 'in `example`', which asks the agent to look elsewhere rather than stating the mechanics inline.

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 one-parameter tool with an output schema, the description covers the essential path: when to call it, how to upload, and what identifier comes back to feed into score_video. Missing link lifetime and file constraints keep it short of complete, but nothing needed to invoke it correctly is absent.

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?

The single parameter (filename, defaulting to video.mp4) has no schema description, and the description never explains what filename is for or how it affects the upload. The format list (MP4/MOV/M4V) only loosely implies that the filename should carry a supported extension. With one undocumented parameter the baseline is not fully earned.

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: creating a one-time upload link for a video file, naming the accepted formats (MP4, MOV, M4V) and the destination (Tuney for scoring). It also explicitly distinguishes itself from import_video, so an agent can separate the two without inspecting schemas.

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?

Gives a concrete when-to-use condition (video is a local file, e.g. attached by the user or in the working directory) and an explicit alternative with its own condition (already online → use import_video). It also names the follow-up step, passing the returned video_id to score_video.

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.