Skip to main content
Glama

run_workflow

Execute a scripted pipeline of macro steps with optional screenshots, supporting progress updates and configurable error handling.

Instructions

Run a scripted pipeline: each step runs a macro, optionally followed by a screenshot. Supports MCP progress when the client requests it. Use verify_each_step=false for faster runs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYesEach step: {"macro", "screenshot_after", "screenshot_capture": "full_screen"|"active_image"|"results_table"}. Defaults use active_image screenshots (headless-safe); use full_screen only with GUI Fiji.
verify_each_stepNoIf true, append screenshot after each step when screenshot_after allows.
continue_on_errorNoIf false, stop after the first failing step and return partial results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesTrue if every step succeeded.
resultsNo
total_stepsNoSet on full completion summary.
failed_stepsNoCount of failed steps on full summary.
completed_stepsNoOn early abort, number of fully completed steps before the failure.
failed_stepNoOn early abort, 1-based index of the first hard failure.
Behavior4/5

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

Discloses MCP progress support, screenshot defaults headless-safe vs GUI, adds context beyond annotations.

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?

Three sentences, no fluff, each sentence provides value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With output schema present, description covers purpose, key behaviors, and a parameter tip; minor gaps on prerequisites.

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

Parameters3/5

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

Schema covers 100% of parameters; description adds only a hint on verify_each_step, baseline 3.

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?

Clearly states 'Run a scripted pipeline' with macros and screenshots, distinguishing from sibling tools like run_macro and run_batch_macros.

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

Usage Guidelines3/5

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

Provides 'Use verify_each_step=false for faster runs' but lacks explicit when-to-use vs alternatives or when-not-to-use.

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/surajinacademia/Fiji_imageJ_mcp'

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