Skip to main content
Glama

Run workflow

run_workflow

Run a workflow. inputs fills its form (see list_workflows): text and choice values as strings, media as one asset id, public https URL or data: URI each. Credits are the sum of its steps; the run reports estimate and actual. With wait=false (default) it returns the queued run with its id; with wait=true it polls up to timeout_s (max 600) and returns the run with outputs (output name -> assets). Runs with video take minutes. item (an item id, slug or @slug in project; see list_items) records the run as a new take of that item; the take is not starred automatically (review with list_takes, keep with star_take).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "run_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNo
slugYes
waitNo
inputsNo
projectNo
timeout_sNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations (non-read-only, open-world, non-destructive), it discloses the async default, that wait=true blocks and polls, the 600s timeout ceiling, that video runs take minutes, that credits are charged as sum of steps and reported as estimate and actual, and that an item run creates an unstarred take. These are exactly the mutation, cost, and latency traits an agent needs.

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?

Dense but front-loaded: the run action comes first, then input formatting, then polling semantics, then item/take side effects. Every clause carries information, though the backtick-dense packing makes it slightly harder to scan than it could be.

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?

For a six-parameter, asynchronous, cost-incurring job tool with an output schema, the description covers inputs, blocking behavior, timeouts, cost reporting, and the take side effect with a path to review it. Nothing an agent needs to invoke it correctly is missing.

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 0%, so the description carries the full burden, and it does so for nearly every parameter: inputs formatting rules per value type (string, one asset id, https URL, or data: URI), item as id/slug/@slug scoped by project, wait default and semantics, and timeout_s maximum. Only 'slug' is left implicit via the list_workflows pointer.

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?

States a specific verb and resource ('Run a workflow') and immediately characterizes the operation as an asynchronous job that may poll and may create a take. It distinguishes itself from siblings by indicating that the run reports both estimate and actual credits (contrasting with an estimate tool) and by referencing the list/star tools for downstream handling.

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?

Gives explicit branching guidance between wait=false (returns queued run with id) and wait=true (polls up to timeout_s), plus a latency warning for video workflows. It points to list_workflows for form fields, list_items for item identifiers, and list_takes/star_take for post-run review, but never explicitly contrasts itself with estimate_workflow or generate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources