Hanzo
Cloud MCPauto

delete_v1_auto_flows_flow

FlowDelete deletes one of the caller's flows.

FlowDelete deletes one of the caller's flows. A foreign id answers 404 and deletes nothing.

Tooldelete_v1_auto_flows_flow
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments1
OperationDELETE /v1/auto/flows/{flow}
Productauto

Arguments

FieldTypeRequiredDefaultDescription
flowstringFlow is the flow's id, taken from the path.

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "delete_v1_auto_flows_flow",
         "arguments": {
           "flow": "<flow>"
         }
       }
     }'

Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →

The operation behind it

OperationRouteProductSummary
cloud_delete_v1_auto_flows_flowDELETE /v1/auto/flows/{flow}autoFlowDelete deletes one of the caller's flows.

The same capability over plain HTTP is in the auto API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page