I'm using LB Android app along some radio apps, it happens I got plenty of songs correctly submitted but also broadcasts I don't want to appear.

It is easier to filter out submissions on client side (i.e. directly from the listen submitter).

The idea is to provide an API endpoint and some web UI to manage "filters".

A filter is basically a tool to match submission payload fields.

According to https://listenbrainz.readthedocs.io/en/latest/users/json.html#payload-json-details it can be anything in track_metadata including additional_info.

So it could look like (just an example, to be refined of course):

{
    "filter1":[
        { "match":"artist_name", "regex":"^A" },
        { "match":"additional_info.tags", "in":[ "blues", "rock" ] },
        { "match":"additional_info.music_service", "eq":"service" }
    ],
    "filter2":[
        { "match":"track_name", "regex":"Z$" }
    ]
}

All clients could query the API to get the filters, and then apply them before submission.
In the future, if deletions get faster, they could also be applied after submission.