Engine filters list moves to the filters field
GET /compose/effects/engine lists every filter an engine effect can name in a new filters field. The old services field stays in the response, always empty.
GET /compose/effects/engine now lists each filter an engine effect accepts in a filters array, by the name the effect’s filter field takes. An engine effect names its filter with filter, for example { "type": "engine", "filter": "cartoon" }.
What to change. The services field is deprecated and always returns an empty array. If your code reads services to build a filter picker, read filters instead. Effects written with the old service field still validate.
The list_job_types MCP tool with effect: "engine" returns the same list. Compose features has every filter with its parameters, and the effects docs show where an engine effect goes in a timeline.