Skip to main content
Glama

list_workflows

Retrieve workflow executions from Conductor with filters for name, status, time range, or text search to monitor and troubleshoot processes.

Instructions

List workflow executions with optional filters. Returns a list of workflow executions matching the criteria.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowNameNoFilter by workflow name/type
statusNoFilter by workflow status (RUNNING, COMPLETED, FAILED, TIMED_OUT, TERMINATED, PAUSED)
startTimeNoFilter workflows started after this time (epoch milliseconds)
endTimeNoFilter workflows started before this time (epoch milliseconds)
freeTextNoFree text search across workflow executions

Implementation Reference

  • Handler implementation for the 'list_workflows' tool. Parses input arguments to build query parameters and calls the Conductor /workflow/search API to retrieve matching workflow executions.
    case "list_workflows": {
      const params: any = {
        start: 0,
        size: 100,
      };
      
      if ((args as any).workflowName) params.workflowType = (args as any).workflowName;
      if ((args as any).status) params.status = (args as any).status;
      if ((args as any).startTime) params.startTime = (args as any).startTime;
      if ((args as any).endTime) params.endTime = (args as any).endTime;
      if ((args as any).freeText) params.freeText = (args as any).freeText;
    
      const response = await conductorClient.get("/workflow/search", { params });
      
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Tool definition including name, description, and input schema for validating parameters used by the list_workflows tool.
      name: "list_workflows",
      description:
        "List workflow executions with optional filters. Returns a list of workflow executions matching the criteria.",
      inputSchema: {
        type: "object",
        properties: {
          workflowName: {
            type: "string",
            description: "Filter by workflow name/type",
          },
          status: {
            type: "string",
            description: "Filter by workflow status (RUNNING, COMPLETED, FAILED, TIMED_OUT, TERMINATED, PAUSED)",
            enum: ["RUNNING", "COMPLETED", "FAILED", "TIMED_OUT", "TERMINATED", "PAUSED"],
          },
          startTime: {
            type: "number",
            description: "Filter workflows started after this time (epoch milliseconds)",
          },
          endTime: {
            type: "number",
            description: "Filter workflows started before this time (epoch milliseconds)",
          },
          freeText: {
            type: "string",
            description: "Free text search across workflow executions",
          },
        },
      },
    },
  • src/index.ts:598-602 (registration)
    Registers the list of available tools (including list_workflows) for the MCP list_tools request.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools,
      };
    });
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. It states the tool returns a list of executions but omits critical details like pagination behavior, rate limits, authentication requirements, or whether it's read-only. For a list operation with zero annotation coverage, this is a significant gap in transparency.

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 two sentences with zero waste—it directly states the purpose and return value. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool's moderate complexity (5 optional parameters) and lack of annotations/output schema, the description is minimally adequate. It covers the basic action and return type but misses behavioral context like pagination or error handling. With no output schema, it should ideally explain the return structure more, but it's passable for a list operation.

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 the schema fully documents all 5 parameters. The description adds no additional meaning beyond implying filtering exists, which is already covered in the schema. This 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 verb ('List') and resource ('workflow executions') with the action of filtering. It distinguishes from siblings like 'search_workflows' by focusing on listing with filters rather than broader search functionality. However, it doesn't explicitly contrast with 'get_workflow_status' or other getters, keeping it at 4 rather than 5.

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 mentions 'optional filters' but provides no guidance on when to use this tool versus alternatives like 'search_workflows' or 'get_workflow_status'. It lacks explicit context about use cases, prerequisites, or exclusions, leaving the agent with minimal direction.

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/opensensor/conductor-mcp'

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