As suggested by @lewis, there are various approaches to implementing routes. If you have yet to work on setting up routes, it might be a good starting point, especially if you need to include inputs in a URL.
Using "...title_like=head&comments_like=today" directly in the URL for specifying logic like "OR" may not be the most optimal choice. It should be determined by your server-side code whether "AND" or "OR" logic is used between the provided parameters.
If the above URL was utilized and your server implemented an "OR" logic, it could lead to confusion among clients who were expecting an "AND" behavior, particularly if they did not refer to your documentation.
An alternative approach would be to include inputs in a body parameter rather than within the URL. Body parameters can accommodate both "AND" and "OR" logic. This method allows you to clearly communicate to users that values from the body will be utilized for "OR" logic, instead of "AND" logic (assuming clients review the documentation).