Skip to main content
Glama

Viddler

by com.viddler

viddler_videos_register

Step 2 of uploading a video: after the file has been PUT to the uploadUrl, call this with the uploadId to create the video record. Returns the video (muxPlaybackId will be 'pending'). Poll viddler_videos_get until muxPlaybackId resolves — processing usually takes under a minute. If title/description are omitted, AI generates them from the video content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional explicit title.
upload_idYesThe uploadId returned by viddler_videos_create_upload.
custom_urlNoOptional custom URL slug.
descriptionNoOptional explicit description.

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that muxPlaybackId will be 'pending' initially, typical processing time under a minute, and AI generation of omitted fields. No annotations provided, so description fully compensates.

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?

Three concise sentences, no unnecessary words, logically ordered from prerequisite to behavior to post-call action.

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?

Complete for a step in a multi-step process; explains return value and polling behavior despite missing output schema. No gaps given the context.

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

Parameters4/5

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

Schema coverage is 100%, baseline 3. Description adds context about upload_id being from previous step and AI fallback for title/description, adding value beyond schema.

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?

Clearly identifies as step 2 of uploading, after file PUT, to create video record. Distinguishes from sibling tools like viddler_videos_create_upload and viddler_videos_get.

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 states when to use (after PUT to uploadUrl), what to do after (poll viddler_videos_get), and optional behavior (AI generates title/description if omitted).

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