Skip to main content
Glama

Viddler

by com.viddler

viddler_videos_create_upload

Step 1 of uploading a video. Returns { uploadId, uploadUrl }. PUT the raw video file bytes to uploadUrl (e.g. curl -X PUT --upload-file video.mp4 '<uploadUrl>' — no auth header needed, the URL is pre-signed). Then call viddler_videos_register with the uploadId to create the video record. Files must be at most 1 GB (1073741824 bytes). Free videos must be at most 10 minutes. Requires a videos:write token.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional title to attach to the upload.
file_size_bytesNoSource file byte count for preflight validation. Send when known; omission supports older clients.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / file_size_bytes
      Added value: +{
+  "description": "Source file byte count for preflight validation. Send when known; omission supports older clients.",
+  "exclusiveMinimum": 0,
+  "maximum": 1073741824,
+  "type": "integer"
+}
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full behavioral burden and does so thoroughly: it discloses the two-step workflow, pre-signed URL behavior, auth requirement, size limit, and free-tier duration limit. This gives an agent a clear model of what happens when the tool is invoked.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence adds value: workflow, return shape, HTTP action, example, constraints, and auth. It is front-loaded with the purpose and remains compact with no filler.

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?

Given no output schema and only two optional simple parameters, the description is complete: it explains the response format, next required action, authentication, and constraints. An agent has everything needed to invoke this step correctly within the larger upload flow.

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 both parameters already have meaningful descriptions. The tool description reinforces the 1 GB limit mentioned in the schema, but does not add substantial new meaning about either parameter beyond what the schema already provides.

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 action ('Step 1 of uploading a video') and a clear resource (creating an upload), with the return shape { uploadId, uploadUrl }. It also points to the sibling tool viddler_videos_register as the next step, which distinguishes it from the registration/creation sibling.

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?

Explicitly describes the usage flow: PUT raw bytes to the returned uploadUrl, then call viddler_videos_register with the uploadId. It also gives a concrete curl example, states the auth requirement (videos:write token), and clarifies that the upload URL is pre-signed so no auth header is needed.

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

All Viddler toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation5/5

Each tool targets a specific action on a distinct resource (access, analytics, feedback, videos). There is no overlap; for example, password protection and custom URL are clearly separate access tools.

Naming Consistency5/5

All tools follow the pattern `viddler_<category>_<verb>_<noun>` with consistent snake_case. Categories are logical (access, analytics, feedback, videos) and verbs are appropriately descriptive (remove, set, get, list, create, etc.).

Tool Count4/5

12 tools is a reasonable number for a video management server. The set is scoped to core operations, not bloated. A few more could be added (e.g., delete), but the count is appropriate for the domain.

Completeness3/5

The tool set covers upload, registration, retrieval, listing, and metadata updates, but lacks a delete video tool. This is a notable gap for a video management server. Other missing operations like trash or restore are not critical, but delete is a basic lifecycle operation.

Resources