@romanmg is correct, of course. More generally ANY list operation can be applied to a single thing because you can always turn a single item into a one-item list with the :make list operator.
This isn’t a hack or workaround — this is how Bubble is designed to work. And it’s documented.
To have redundant single-item actions for existing listwise actions does not seem desirable to me. It would just add clutter.
The part that isn’t documented is sort of the “why?” of listwise operations. List operators are where we find looping and iteration features of Bubble.
We often see people ask about doing something iteratively. Sometimes, the iteration is not available in vanilla Bubble. But with respect to things and the database, most of the iterative operations you’d need to perform are actually already available.
The trick is, in array-oriented systems, you have to think about iteration differently than in other languages/systems. Iteration starts with having an existing array, upon which the iterative action can be done.
(For a practical example of this in Bubble, have a look at what I suggested to @zelus_pudding here: How to create a Thing, multiple times?)
As an array-oriented system, Bubble is currently slightly incomplete. Most noteably it’s missing a facility to create and auto-populate lists of native data type with arbitrary lengths.
(Like create a create a list of numbers 0 to 99, incremented by 1. Or, create a list of dates today to tomorrow, incremented by 30 minutes.)
In systems that offer array operations instead of loops — which is what Bubble does — such features are kind of essential. There are workarounds for this, but they are either manual (make these things manually in your database) or involve using Toolbox.