Skip to main content
Glama

upload_video

Upload a local video file to ComfyUI's input directory for use in video-loading nodes. Handles remote upload via HTTP or local copy.

Instructions

Upload a local video file (.mp4, .mov, .webm, .avi, .mkv, .m4v) to the connected ComfyUI's input/ directory for use in video-loading nodes such as VHS_LoadVideo (ComfyUI-VideoHelperSuite). Tries an HTTP multipart upload first (works against a remote --comfyui-url instance), then falls back to a local filesystem copy when COMFYUI_PATH is set. Returns the stored filename. Use upload_image for images or upload_audio for audio.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_pathYesAbsolute path to the local file to upload
filenameNoOverride the filename in ComfyUI's input/ directory. Auto-detected from source path if omitted.
Behavior5/5

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

With no annotations, the description fully discloses behavior: tries HTTP multipart upload first, falls back to local copy, and returns the stored filename. Also lists supported file formats.

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?

Two sentences, front-loaded with purpose, each sentence provides essential information without redundancy.

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?

Covers purpose, file formats, mechanism, return value, and sibling differentiation. Without output schema, it still provides sufficient guidance for an upload tool.

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%, but the description adds value by explaining the fallback behavior and return value, going beyond basic parameter descriptions.

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?

The description clearly states the tool uploads a video file to ComfyUI's input/ directory, lists supported formats, and distinguishes itself from sibling tools upload_image and upload_audio.

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

Usage Guidelines4/5

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

Explains when to use (for videos) and names alternatives for images/audio. Describes the upload mechanism with fallback, but does not explicitly state when not to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/artokun/comfyui-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server