Skip to main content
Glama

download_model

Downloads a model file into the folder ComfyUI loads from, with resume support and dry-run checks.

Instructions

Download a model file into the folder ComfyUI will actually load it from.

Meant for the models a workflow declares on its own loaders: at detail="full" get_workspace_graph reports each node's properties.models as [{name, url, directory}], and directory is this tool's folder. Graphs without that property usually ship a "Model Links" note saying the same thing in prose. Either way, check what is already there with list_models(folder) first and fetch only the rest.

Where the file lands is decided by ComfyUI, not by this server: the directory list honours extra_model_paths.yaml, so it is routinely on another drive entirely, and a model written anywhere else is invisible however right the bytes are. The reply always names the directory it chose.

Interrupted transfers resume: the bytes go to a .part file beside the target and re-issuing the same call continues from where it stopped, so a failure costs the remainder rather than the whole file.

Args: url: direct link to the file, as written in the note. folder: ComfyUI model folder, e.g. 'vae' or 'diffusion_models'. list_models() with no arguments lists the valid names. filename: name to save as. Defaults to the last segment of the URL. A 'subdir/name.safetensors' is allowed; ComfyUI loads those. directory: which of the folder's registered directories to use. Defaults to the first one that exists, which is what ComfyUI's own is_default ordering intends. wait: wait for the download to finish. False returns immediately and the transfer keeps running, so get_download_progress reports it - prefer that for anything large, since a multi-gigabyte file outlasts most tool-call deadlines. overwrite: fetch again even though the file is already there. dry_run: report size, checksum and destination without fetching anything. Worth doing first: a link in a note is often several gigabytes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
waitNo
folderYes
dry_runNo
filenameNo
directoryNo
overwriteNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description uniquely carries the full burden of behavioral disclosure. It covers critical quirks: ComfyUI decides the actual directory honoring extra_model_paths.yaml, interrupted transfers resume via .part files, wait vs. asynchronous behavior, and that the reply names the chosen directory. No annotation contradiction exists.

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 long but every sentence adds value. It is front-loaded with a crisp purpose, then logically flows into usage context, behavioral caveats, and a clear Args list. The formatting with bolded keys and defaults makes it scannable despite its length.

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?

The tool is complex (7 params, ComfyUI integration, resumable downloads), and the description covers all aspects: purpose, prerequisites (checking list_models), alternatives, error-prone behaviors, and parameter usage. An output schema exists, so not detailing return values is appropriate.

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

Parameters5/5

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

Schema has 0% coverage, so the description must and does explain every parameter in depth. It clarifies url's provenance, folder examples, filename defaults and subdirectory support, directory selection logic, wait's async behavior, overwrite semantics, and dry_run's purposeful size/checksum preview.

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 opens with a specific verb+resource: 'Download a model file into the folder ComfyUI will actually load it from.' It clearly distinguishes from siblings like list_models and get_download_progress by focusing on the actual download action and its integration with ComfyUI's model folders.

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?

Provides explicit guidance: 'check what is already there with list_models(folder) first', recommends dry_run ('Worth doing first'), and directs large downloads to get_download_progress ('prefer that for anything large'). It also explains when the tool is intended ('for the models a workflow declares on its own loaders').

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/pytraveler/local-comfyui-mcp'

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