It would be nice, eh? Unfortunately, collection list filters cannot be set dynamically from a client-side script.
What I have done in extreme cases is to create the “key” as its own table, so that each has its own page. In your example;
/member/mem_clcdq3...
Then ref other CMS items to it. On that page, in hidden collection lists, you could then create the data you want as hidden JSON on that page.
When you need it, it’s now accessible using AJAX and a bit of DOM parsing.
A bunch of hoops to jump through, and it’s not suitable for anything even remotely sensitive. But in some situations, it’s worked great.