Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When using the awslocal scheduler API or CLI, some arguments are being ignored entirely (but not all) when attempting to limit results (either by MaxResults or by NamePrefix).

The AWS CLI argument is --max-items while API is MaxResults. --max-items is working as expected when using awslocal.

This affects both ListSchedules and ListScheduleGroups.

Expected Behavior

localstack-maxitems.txt
localstack-scheduler.txt

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

How are you starting localstack (e.g., bin/localstack command, arguments, or docker-compose.yml)

docker run localstack/localstack

Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

awslocal scheduler list-schedule-groups --name-prefix blabla
awslocal scheduler list-schedules --name-prefix blabla

/schedules?MaxResults=1

Environment

- OS: Ubuntu 24 & Windows WSL2 Ubuntu
- LocalStack: Community
  LocalStack version: 4.3
  LocalStack Docker image sha:
  LocalStack build date:
  LocalStack build git hash:

Anything else?

No response