Skip to main content
Glama

Delete workflow

campaignstack_delete_workflow
Destructive

Permanently delete one workflow and its associated records. Requires confirmed:true. Use edit_workflow set_enabled:false to pause without deleting history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmedYesThis permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.
workflowIdYes
workspaceIdNoWorkspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
resultsNo
warningsNo
workflowIdNo
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / confirmDelete
      Removed value: -{
      -  "const": true,
      -  "description": "This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.",
      -  "type": "boolean"
      -}
    • addedInput schema / properties / confirmed
      Added value: +{
      +  "const": true,
      +  "description": "This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "workflowId",
      -  "confirmDelete"
      -]New value: +[
      +  "workflowId",
      +  "confirmed"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach."New value: +"Workspace ID. Omit it when this connection reaches one workspace: a workspace key (cs_) is bound to its own, and a user key (csu_) or connected app whose person belongs to exactly one workspace defaults to that one. Required only when the person belongs to several; the error then lists them, and campaignstack_whoami reports them too."
  3. Changed9 schema fields changed
    • addedInput schema / properties / confirmDelete
      Added value: +{
      +  "const": true,
      +  "description": "This permanently deletes a root record. Before calling it, name exactly what will be deleted, explain that it cannot be undone, and wait for an explicit yes.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / workspaceId
      Added value: +{
      +  "description": "Workspace ID. REQUIRED for a user key (csu_), which spans every workspace you belong to; omitted for a workspace key (cs_), which is bound to one and ignores this argument. campaignstack_whoami reports which kind of key you are holding and, for a user key, the workspaces it can reach.",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "workflowId"
      -]New value: +[
      +  "workflowId",
      +  "confirmDelete"
      +]
    • addedOutput schema / properties / ok
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / results
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • removedOutput schema / properties / workflowId / anyOf
      Removed value: -[
      -  {
      -    "anyOf": [
      -      {
      -        "not": {}
      -      },
      -      {
      -        "type": "string"
      -      }
      -    ]
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / workflowId / type
      Added value: +"string"
    • addedOutput schema / properties / workspaceId
      Added value: +{
      +  "type": "string"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": true,
      +  "properties": {
      +    "workflowId": {
      +      "anyOf": [
      +        {
      +          "anyOf": [
      +            {
      +              "not": {}
      +            },
      +            {
      +              "type": "string"
      +            }
      +          ]
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context beyond them: the deletion is permanent AND cascades to associated records, and a confirmation flag is mandatory. The only gap is that it doesn't describe the failure/response shape, which is partly covered by the output schema.

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?

Two short sentences, both load-bearing: the first defines the action and its blast radius, the second defines the safer alternative. No filler. Slightly terse on return/cascade edge cases, but nothing is wasted.

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

Completeness4/5

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

With annotations covering the destructive profile, an output schema covering returns, and 3 params of which two are documented in the schema, the description's remaining job is scope and safety framing — both delivered. Only minor omission is guidance on what happens on a failed/partial cascade.

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 coverage is 67%, with the confirmed and workspaceId parameters already well documented in the schema (including the multi-workspace fallback behavior). The description adds the confirmed:true requirement, but says nothing new about workflowId or workspace resolution, so this sits at the baseline where the schema does most of the work.

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

Purpose5/5

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

States a specific verb+resource (delete one workflow) and immediately scopes it ("and its associated records"), which is the key semantic difference from a soft disable. It also names the sibling alternative, so an agent can distinguish it from edit_workflow without opening either schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use edit_workflow set_enabled:false when the goal is pausing without losing history, and use this tool only for permanent removal. The precondition (requires confirmed:true) is also stated up front.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources