Skip to main content
Glama

run_template

Execute a named workflow template with optional widget overrides. Enqueues the resolved graph and returns a prompt ID, or blocks for outputs when wait is true.

Instructions

ONE-SHOT: run a named workflow template (a bundled pack from list_packs) with optional overrides. Resolves the template's expert graph, applies overrides, and enqueues it — replacing the manual read_pack_workflow → modify_workflow → enqueue_workflow chain. Override keys are '.' (e.g. {'6.text': 'a cat', '3.seed': 42}) — the SAME keys the companion get_template_schema tool reports (when available), so schema→run round-trips; only widget values can be overridden, never graph connections. By default returns {prompt_id} immediately; pass wait:true to block until the job completes and return its outputs (images etc.). Unresolvable template names return a clear error with near-matches.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoBlock until the job completes and return its outputs. Default false: return {prompt_id} immediately.
templateYesTemplate name — a bundled pack directory (from list_packs), e.g. 'anima-txt2img'.
overridesNoWidget overrides keyed '<nodeId>.<widget_name>' (get_template_schema's keys), e.g. {'6.text': 'a red fox', '3.steps': 20}.
timeout_sNoMax seconds to wait when wait:true (default 300). On timeout the job keeps running; poll get_job_status.
disable_random_seedNoIf true, do not randomize seed values (combine with a seed override to reproduce exactly).
Behavior5/5

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

With no annotations, the description fully discloses behavior: it resolves the expert graph, applies overrides, enqueues, and returns {prompt_id} unless wait:true blocks for outputs. It mentions error handling with near-matches and timeout polling behavior, leaving no hidden surprises.

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

Conciseness4/5

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

The description is a single, moderately long paragraph but front-loaded with 'ONE-SHOT:' to immediately convey purpose. Every sentence adds necessary detail; however, it could be slightly more structured (e.g., bullet points) without losing information.

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 5 parameters with 100% schema coverage and no output schema, the description compensates fully by explaining override format, wait behavior, error handling, and links to companion tools. It covers all necessary aspects for correct tool invocation.

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 meaning beyond basic schema descriptions: it details the override key format (<nodeId>.<widget_name>), the round-trip with get_template_schema, and wait vs. immediate return. This elevates from baseline 3 to 4.

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 runs a named workflow template with optional overrides, using the verb 'run' and specifying the resource as 'workflow template'. It distinguishes from sibling tools like read_pack_workflow, modify_workflow, and enqueue_workflow by explicitly replacing their chain.

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?

The description provides explicit when-to-use context: it's a one-shot alternative to the manual chain, specifies override format referencing get_template_schema, and explains optional wait behavior with timeout advice. It also clarifies that only widget values can be overridden, not graph connections, setting clear boundaries.

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