route_update

Modify an existing Edge Routine route configuration by updating its enable status, rule, routine name, bypass, and sequence in the ESA MCP Server.

Instructions

Modify the configuration of an existing Edge Routine route.

Input Schema

Name	Required	Description
`bypass`	Yes	The bypass of the route
`configId`	Yes	The ID of the config
`routeEnable`	Yes	The enable of the route
`routeName`	Yes	The name of the route, use to identify the route.
`routineName`	Yes	The name of the routine
`rule`	Yes	The rule of the route
`sequence`	No	The sequence of the route, if not passed, default is the current number of routes
`siteId`	Yes	The ID of the site

Input Schema (JSON Schema)

{
  "properties": {
    "bypass": {
      "description": "The bypass of the route ",
      "enum": [
        "on",
        "off"
      ],
      "type": "enum"
    },
    "configId": {
      "description": "The ID of the config",
      "type": "number"
    },
    "routeEnable": {
      "description": "The enable of the route",
      "enum": [
        "on",
        "off"
      ],
      "type": "enum"
    },
    "routeName": {
      "description": "The name of the route, use to identify the route.",
      "type": "string"
    },
    "routineName": {
      "description": "The name of the routine",
      "type": "string"
    },
    "rule": {
      "description": "The rule of the route",
      "type": "string"
    },
    "sequence": {
      "description": "The sequence of the route, if not passed, default is the current number of routes",
      "type": "number"
    },
    "siteId": {
      "description": "The ID of the site",
      "type": "number"
    }
  },
  "required": [
    "siteId",
    "configId",
    "routeName",
    "routeEnable",
    "rule",
    "routineName",
    "bypass"
  ],
  "type": "object"
}

ESA MCP Server

route_update

Instructions

Input Schema

Input Schema (JSON Schema)

Other Tools from ESA MCP Server

Related Tools

MCP directory API