We want to standardize the way that admin users can describe and interact with the client commands. We are proposing to generalize the filters introduced in CLIENT KILL so that it also works to count the number of clients as well

In the end, we will support the following 4 commands.

Client COUNT <filters>
CLIENT KILL <filters>
CLIENT LIST <filters>
CLIENT DESCRIBE <selectors> FILTER <filters>

The supported filters will be:

TYPE [NORMAL|MASTER|SLAVE|REPLICA|PUBSUB]
USER username
ADDR ip:port
LADDR ip:port
SKIPME [yes |no]
ID client-id
ID client-id [client-id ...], for compatibility reasons with client list, client-id must be specified last.
pattern pattern the client must subscribe to
channel channel the client must subscribe to
SHARD-CHANNEL <shard channel the client must subscribe to`
FLAGS Client must include this flag, this option can be repeated
NAME client name
MIN-IDLE minimum idle time of the client
CLIENT DESCRIBE will allow you specify what fields you want from the client. The supported selectors will be the same as the above mentioned filters, in addition to the fields currently supported from https://redis.io/commands/client-list/.

Example command:

CLIENT DESCRIBE SELECT ID ADDR FILTER MIN-AGE 100 

The new CLIENT DESCRIBE command will return in a RESP list or map response, while the client list will continue to return a textual response. @itamarhaber I feel like you talked about something else, but I didn't understand.