PRACTICAL FIELD GUIDE
Multiple REST filters combine with AND
Multiple supported filters narrow a result together rather than automatically creating an OR expression. Confirm that this matches the screen's intended search behavior.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Translate the user-facing condition into explicit logical terms.
- Use supported filters when the condition is an intersection.
- For alternatives, design a supported approach and account for deduplication, ordering and request cost if multiple requests are needed.
What this looks like
ILLUSTRATIVE EXAMPLE
Filtering status=active and owner_id=one-user requests rows satisfying both conditions, not rows satisfying either.
A boundary to keep clear
Do not claim arbitrary OR querying is available unless the current generated contract actually provides it.
MCPBackend context
Use get_project_api or the dashboard's generated OpenAPI contract for your project's exact data-plane routes. Machine keys and end-user tokens have different access models. Treat error status and JSON code together, keep credentials out of URLs, and test against disposable records before changing real data.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.