Skip to main content
Glama

update_workflow

Modify existing workflows in Automatisch by updating names, descriptions, or activation status to adapt automation processes as business needs change.

Instructions

Update an existing workflow

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workflowIdYesWorkflow ID to update
nameNoNew workflow name
descriptionNoNew workflow description
activeNoWorkflow active status

Implementation Reference

  • src/handlers.ts:65-90 (registration)
    Registration of the 'update_workflow' tool in the ListToolsRequestHandler, including name, description, and input schema definition.
    {
      name: "update_workflow",
      description: "Update an existing workflow",
      inputSchema: {
        type: "object",
        properties: {
          workflowId: {
            type: "string",
            description: "Workflow ID to update"
          },
          name: {
            type: "string",
            description: "New workflow name"
          },
          description: {
            type: "string",
            description: "New workflow description"
          },
          active: {
            type: "boolean",
            description: "Workflow active status"
          }
        },
        required: ["workflowId"]
      }
    },
  • The handler logic in CallToolRequestHandler for 'update_workflow', which invokes the API helper to update the workflow and returns the JSON result.
    case "update_workflow":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(await main.api.updateWorkflow(args?.workflowId, args), null, 2)
          }
        ]
      };
  • API helper function stub for updateWorkflow, called by the tool handler. Actual logic is placeholder.
    updateWorkflow: async function(workflowId: any, data: any) {
      // ... copy updateWorkflow logic from index.ts ...
    },
  • Server instance exposes the api helpers (including updateWorkflow) to the handlers via 'main.api'.
    public api = apiHelpers(this);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'update' which implies mutation, but doesn't cover permissions needed, whether changes are reversible, side effects (e.g., on active workflows), or response format. For a mutation tool with zero annotation coverage, this is inadequate.

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, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse. Every word earns its place, though it could benefit from additional context.

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 complexity (mutation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain what 'update' entails behaviorally, potential impacts, or return values. For a tool that modifies workflows, more context is needed to guide safe and effective use.

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 4 parameters (workflowId, name, description, active). The description adds no parameter-specific information beyond what the schema provides, such as format constraints or examples. This meets the baseline for high schema coverage.

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 ('update') and resource ('existing workflow'), which is clear but basic. It doesn't differentiate from sibling tools like 'create_workflow' or 'delete_workflow' beyond the verb, and lacks specificity about what aspects can be updated. This is a minimal viable description that avoids tautology but provides no additional context.

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 like 'create_workflow' or 'delete_workflow'. The description doesn't mention prerequisites (e.g., needing an existing workflow ID) or contextual cues for selection. This leaves the agent to infer usage solely from the tool name and schema.

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