When creating a media type you are limited to the parameters being a combined length of 255 characters.

This will allow media types to be created with a larger set of parameters, instead of encoding them in the message of the action for the media type processor to handle.

A common thing for us to do is create incidents and put the following in the message for the incident handler to digest:

action_id:{ACTION.ID}
event_id:{EVENT.ID}
trigger_id:{TRIGGER.ID}
incident_hostname:{HOST.HOST}
incident_source:Zabbix
incident:create
incident_requester:Zabbix
incident_severity:{TRIGGER.SEVERITY}
incident_summary:{HOST.HOST}: {EVENT.NAME} [{TRIGGER.SEVERITY}]
incident_classification_1:Infrastructure
incident_classification_2:Storage
incident_classification_3:Backup system Avamar
incident_impact:4
incident_priority:3
incident_affected_service:Server
incident_assignment_group:ICT OPS Operations Centre
incident_description:<<<<

Something goes in here as the incident description etc...

incident_description:>>>>

What this means is in every action we have to replicate this data in the message, even worse if we change things we have to do it everywhere.

Having the ability to put this in the media type as parameters will mean one spot to change with greater flexibility.