Skip to main content
Glama
workflow86oss

Workflow86 MCP Server

Official

run-workflow

Start a workflow by specifying its ID and starting component. Optionally set version and placeholder values to customize execution.

Instructions

A command for starting a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesThe ID of the workflow to run
componentIdYesUUID identifier of the component to start running from Example: 3fa85f64-5717-4562-b3fc-2c960000afa6
workflowVersionNoWorkflow version to run. It could be a integer version or 'DRAFT' or 'PUBLISHED'. If DRAFT OR PUBLISHED, will run latest version of the project with the respective status
placeholderValuesNoA object containing placeholder keys and values to override values from the original session. - Keys must be from the set of placeholders available to the specified component. - All keys are optional at the API level, but omitting them may of course cause the workflow to fail. - Values are validated against the placeholder type. - datetime placeholders MUST be in ISO-8601 format, but may omit timezone, offset, or the whole time portion. - list placeholders MUST EITHER be sent as a JSON List or a Bracketed String (see example). - Values may not be sent as JSON objects, instead keys should use dotted form.
Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It fails to mention side effects, permissions, asynchronous behavior, or whether the workflow runs in a new or existing session.

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 concise sentence, but it sacrifices essential detail. It is front-loaded but too brief for a tool with 4 parameters and no annotations.

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

Completeness2/5

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

Given the complexity (4 parameters, nested objects, no output schema, no annotations), the description is incomplete. It does not explain return values, possible errors, or lifecycle implications.

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 description coverage is 100%, so baseline is 3. The tool description adds no parameter meaning beyond the schema; it does not mention parameters at all.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool starts a workflow, providing a specific verb and resource. However, it lacks differentiation from sibling tools like rerun-workflow, reducing precision.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as rerun-workflow or list-workflows. No prerequisites or contextual hints are provided.

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/workflow86oss/mcp-server'

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