Skip to main content
Glama

delete_workflow

Remove a workflow from the Automatisch automation platform by specifying its ID to manage and organize your automated processes.

Instructions

Delete a workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesWorkflow ID to delete

Implementation Reference

  • src/handlers.ts:91-104 (registration)
    Registration of the 'delete_workflow' tool in the list of tools, including its name, description, and input schema requiring a workflowId.
    {
      name: "delete_workflow",
      description: "Delete a workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "Workflow ID to delete"
          }
        },
        required: ["workflowId"]
      }
    },
  • MCP tool handler dispatch for 'delete_workflow': calls main.api.deleteWorkflow with workflowId argument and returns JSON response.
    case "delete_workflow":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.deleteWorkflow(args?.workflowId), null, 2)
          }
        ]
      };
  • Core API handler function for deleteWorkflow (currently a placeholder stub referencing logic from index.ts).
    deleteWorkflow: async function(workflowId: any) {
      // ... copy deleteWorkflow logic from index.ts ...
    },
  • apiHelpers factory function that provides the api object used by handlers, including deleteWorkflow method.
    export function apiHelpers(main: any) {
      return {
        apiRequest: async function(endpoint: any, options: any = {}) {
          // ... copy apiRequest logic from index.ts ...
        },
        listWorkflows: async function(args: any = {}) {
          // ... copy listWorkflows logic from index.ts ...
        },
        getWorkflow: async function(workflowId: any) {
          // ... copy getWorkflow logic from index.ts ...
        },
        createWorkflow: async function(data: any) {
          // ... copy createWorkflow logic from index.ts ...
        },
        updateWorkflow: async function(workflowId: any, data: any) {
          // ... copy updateWorkflow logic from index.ts ...
        },
        deleteWorkflow: async function(workflowId: any) {
          // ... copy deleteWorkflow logic from index.ts ...
        },
        listConnections: async function(args: any = {}) {
          // ... copy listConnections logic from index.ts ...
        },
        createConnection: async function(data: any) {
          // ... copy createConnection logic from index.ts ...
        },
        listExecutions: async function(args: any = {}) {
          // ... copy listExecutions logic from index.ts ...
        },
        getAvailableApps: async function(args: any = {}) {
          // ... copy getAvailableApps logic from index.ts ...
        },
        testWorkflow: async function(workflowId: any, testData: any = {}) {
          // ... copy testWorkflow logic from index.ts ...
        },
        getWorkflowsOverview: async function() {
          // ... copy getWorkflowsOverview logic from index.ts ...
        },
        getConnectionsOverview: async function() {
          // ... copy getConnectionsOverview logic from index.ts ...
        },
        getRecentExecutions: async function() {
          // ... copy getRecentExecutions logic from index.ts ...
        }
      };
  • Initialization of the 'api' property on the server instance using apiHelpers, making it available to handlers as main.api.
    public api = apiHelpers(this);
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete' but doesn't disclose behavioral traits such as whether deletion is permanent, reversible, requires specific permissions, affects related data (e.g., executions), or has side effects. This is a significant gap for a destructive operation with zero annotation coverage.

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 extremely concise ('Delete a workflow'), with no wasted words. It's front-loaded and efficiently conveys the core action, though this brevity contributes to gaps in other dimensions. Every sentence (here, one) earns its place by stating the purpose directly.

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't explain what deletion entails, return values, error conditions, or dependencies on sibling tools. For a mutation tool with high complexity risk, more context is needed to guide safe usage.

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 description coverage is 100%, with the single parameter 'workflowId' documented in the schema. The description doesn't add any parameter details beyond what the schema provides, but with only one parameter and high coverage, the baseline is high. No compensation is needed, but no extra value is added either.

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

Purpose3/5

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

The description states the action ('Delete') and resource ('a workflow'), which is clear but minimal. It doesn't differentiate from siblings like 'update_workflow' or specify what 'delete' entails (e.g., permanent removal vs. archiving). While it avoids tautology, it lacks specificity about scope or consequences.

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 is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing the workflow ID from 'get_workflow' or 'list_workflows'), exclusions, or comparisons to siblings like 'update_workflow' for modifications. The agent must infer usage from context alone.

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