Skip to main content
Glama

list_workflows

Retrieve and filter workflows from the Automatisch automation platform to view active, inactive, or all workflows with optional result limits.

Instructions

List all workflows in Automatisch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter workflows by status
limitNoLimit number of results

Implementation Reference

  • The MCP tool handler for 'list_workflows' which invokes the API helper main.api.listWorkflows and returns the result as JSON text.
    case "list_workflows":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.listWorkflows(args), null, 2)
          }
        ]
      };
  • Input schema definition for the 'list_workflows' tool, specifying optional status filter and limit parameters.
    inputSchema: {
      type: "object",
      properties: {
        status: {
          type: "string",
          enum: ["active", "inactive", "all"],
          description: "Filter workflows by status"
        },
        limit: {
          type: "number",
          description: "Limit number of results"
        }
      }
    }
  • src/handlers.ts:10-27 (registration)
    Registration of the 'list_workflows' tool in the ListToolsRequestHandler response, including name, description, and schema.
    {
      name: "list_workflows",
      description: "List all workflows in Automatisch",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: ["active", "inactive", "all"],
            description: "Filter workflows by status"
          },
          limit: {
            type: "number",
            description: "Limit number of results"
          }
        }
      }
    },
  • API helper method listWorkflows that is called by the tool handler. Currently a stub awaiting implementation logic.
    listWorkflows: async function(args: any = {}) {
      // ... copy listWorkflows logic from index.ts ...
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, if it requires permissions, how results are ordered or paginated, or any rate limits. For a list tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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?

The description is a single, direct sentence with zero waste—it states the purpose without unnecessary words. It's appropriately sized for a simple list tool and front-loaded with the core action, making it easy to parse quickly.

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 of listing workflows (which may involve filtering, pagination, or permissions), the description is incomplete. With no annotations and no output schema, it fails to address key aspects like return format, error handling, or behavioral traits. It relies too heavily on the input schema alone, leaving gaps for an AI agent to infer usage.

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?

The schema description coverage is 100%, with clear descriptions for both parameters ('status' and 'limit'), including an enum for 'status'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema does the heavy lifting.

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 action ('List') and resource ('all workflows in Automatisch'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_workflow' or 'list_executions', but the verb 'List all' suggests a comprehensive retrieval rather than fetching a single item or related executions.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_workflow' for a single workflow or 'list_executions' for workflow runs. It lacks context about prerequisites, such as whether authentication is needed or if it's the primary method for browsing workflows.

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

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