## Check for existing issues

- [x] I searched the existing issues and checked that this is not a duplicate

## What happened?

`GET /v1/containers?after=cursor&limit=20&order=desc` places the pagination values under `query_params`, while the provider SDK expects `after`, `limit`, and `order` as top-level list arguments

As a result, the LiteLLM Proxy container list and dynamic container file-list routes can ignore the requested cursor, limit, or sort order and return the provider defaults

This affects the container endpoints in the LiteLLM Proxy

## Steps to Reproduce

1. Start LiteLLM Proxy with a provider configuration that supports the container endpoints 2. Call `GET /v1/containers?after=cursor&limit=20&order=desc` 3. Inspect the provider call arguments 4. Observe that the pagination values are nested under `query_params` instead of being passed as top-level arguments

## Relevant log output

```text Received: {"query_params": {"after": "cursor", "limit": 20, "order": "desc"}} Expected: {"after": "cursor", "limit": 20, "order": "desc"} ```

## What part of LiteLLM is this about?

Proxy

## LiteLLM version

litellm_oss_daily_2026_07_20

## Proposed resolution

Validate `after`…