Get Notification Type Fields
getNotificationTypeFieldsReturns required and optional configuration fields, with meanings, for a notification type so you can create or update Uptime Kuma notification settings correctly.
Instructions
Describes the config fields one notification type takes: which are required, which are optional and what each means. Call it before createNotification, or before updateNotification changes a type or its settings: field names are case-sensitive and Uptime Kuma saves a misspelled one without complaint. The common types are covered; for the rest it says so, and their field names can be copied from an existing channel in listNotifications. Type names come from listNotificationTypes.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"type": "<type>"
},
"name": "getNotificationTypeFields"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | The notification type, e.g. slack, smtp, PagerDuty. Use listNotificationTypes for all options. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The name Uptime Kuma shows for this type | |
| type | Yes | ||
| notes | Yes | ||
| optional | Yes | Other fields the type reads | |
| required | Yes | Fields the type cannot send without. A create without them is refused. | |
| documented | Yes | false when this server has no field table for the type | |
| commonFields | Yes | Arguments of createNotification / updateNotification that every type takes, outside config |