Skip to main content
Glama

load_workspace

Open a saved workflow from the workspace into a new ComfyUI tab, with backup of the current canvas before replacing.

Instructions

Open a saved workflow in the browser, as a tab in the ComfyUI window.

The other half of save_workspace, and the way to put a workflow file under the workspace tools: load it, edit it with them, save it back. Without this they can only reach whatever the user happened to have open.

Both formats work and neither has to be named - a file in workflows/ is API format, one in exports/ is UI format, and this reads which it is. UI format keeps the layout it was saved with; API format has none, so ComfyUI lays it out itself and the result is tidy rather than familiar.

It opens a tab rather than replacing the one on screen. ComfyUI reuses a tab only when its own workflow store already knows the name, and that store does not sync from this server's workflows directory - so a file usually arrives in a new tab marked unsaved, with the workflow that was on screen still open in its own. Loading that same file again reuses the tab it made the first time, and that one is replaced. The reply reports the tabs and whether one was added; switch_workspace_tab moves between them afterwards.

A name ComfyUI already knows is refused. It resolves the name against its own saved workflows rather than against the directory the file came from, so a file whose name matches one of the user's workflows would fill that workflow's tab instead of opening one - leaving it looking edited, one Ctrl+S from overwriting their work. Rename the file, or pass force when replacing that workflow is the actual intent.

This is not undoable. ComfyUI resets the undo history when a workflow is loaded, so Ctrl+Z will not bring the previous canvas back. That is what the backup is for, and it is the reused-tab case it covers: the canvas is written to the export directory first and the reply names the file.

Args: name: the file, with or without .json. Looked for in the workflows directory first, then the export directory; an absolute path also works. backup: write the current canvas to the export directory before replacing it. Leave it on unless the canvas is known to be worth nothing. force: load even when ComfyUI already has a saved workflow of this name, taking over its tab. Only when replacing that workflow is meant. client_id: which tab to load into; defaults to the most recently focused one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
forceNo
backupNo
client_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description is exceptionally transparent about non-obvious behavior: it opens a tab rather than replacing the current one, explains when tab reuse occurs, warns that the operation is not undoable, and documents the backup mechanism. Since no annotations are provided, the description fully bears the burden of behavioral disclosure and does so thoroughly.

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?

While the description is lengthy, the length is justified by the complexity of the behavior. It starts with a summary, then covers important edge cases in focused paragraphs, and ends with a clear Args section. Each sentence adds value, and the structure makes the information easy to parse.

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 description covers all critical context: file format differences, tab behavior, naming conflicts, undo behavior, backup fallback, and parameter semantics. It also references what the reply contains, such as tab information and backup file naming, which aligns with the existing output schema. This is a comprehensive description for a tool with this level of behavioral nuance.

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?

The input schema provides zero description coverage (0%), but the description's Args section compensates fully by explaining what each parameter means, including name resolution order, backup behavior and default, force semantics, and client_id targeting. This goes well beyond the raw schema and gives the agent the necessary context to invoke each parameter correctly.

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 clear, specific action: 'Open a saved workflow in the browser, as a tab in the ComfyUI window.' It distinguishes this tool from save_workspace and other workspace tools by explaining its role as the counterpart that loads saved workflow files into the UI.

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?

It provides strong guidance on when to use this tool: it is the way to put a workflow file under workspace tools, and it explains why this capability matters when the user has no workflow open. It also gives explicit caveats about refusal when ComfyUI already knows the name, advises renaming or using 'force', and points to switch_workspace_tab as the follow-up for navigating tabs.

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