Describe the bug

When using thesearch_repositories tool, the server returns a very large response with all matching repositories at once, without pagination or limiting the results to a manageable amount. This makes it difficult to process and use the data effectively, especially in contexts where the response needs to be displayed or processed in a user-friendly way.

Affected version

server version v0.1.0 (b89336793c5bc9b9abdd5100d876babbc1031f5d) 2025-04-04T15:38:19Z

Steps to reproduce the behavior

1. Use thesearch_repositories tool with a somewhat generic query like "MCP Model Context Protocol"
2. Receive a response with a large number of repositories (30+ in my case)
3. The entire response is returned at once without pagination, making it difficult to manage

Expected vs actual behavior

Expected behavior:

• The server should return a limited number of results (e.g., 10 repositories)
• The response should include pagination information (e.g., total count, current page, next page token)
• There should be a way to request subsequent pages of results

Actual behavior:

• The server returns all matching repositories in a single response
• No pagination mechanism is provided
• The response can be extremely large and unwieldy for common search terms

Logs

The response included 30+ repositories with full details for each, resulting in a very large JSON payload. The beginning of the response looked like this:

{"total_count":1746,"incomplete_results":false,"items":[{"id":905016458,"node_id":"R_kgDONfF0ig","owner":{"login":"lastmile-ai","id":123273171,"node_id":"O_kgDOB1j_0w","avatar_url":"https://avatars.githubusercontent.com/u/123273171?v=4","html_url":"https://github.com/lastmile-ai","gravatar_id":"","type":"Organization","site_admin":false,...

Note that while the response includes"total_count":1746, it doesn't provide any way to paginate through these results.