Follow-up to #107: /v1/coding_plan/search API needs pagination support

从 MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py 开始，检查 web_search 工具，然后跟踪代理 /v1/coding_plan/search 的底层 API gateway。确认可以在哪里实现分页参数和响应行为。完成标准是 API 接受有文档说明的 count 以及 page 或 offset 机制，之后 CLI 和 SDK 才能提供相匹配的选项。

Follow-up to #107

Issue #107 (closed by docs-only PR) asked for pagination on mmx search query because the API returns at most 10 results per call.

Investigation result

The /v1/coding_plan/search endpoint does not currently expose any pagination parameter. The canonical reference client (MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py, web_search) only sends {"q": query} and the response is just { organic: [...], related_searches: [...] } — no count, page, limit, or offset is accepted or returned.

In other words, the 10-result cap is a hard limit imposed by the API, not by the CLI. The CLI cannot expose pagination flags that the server will not honor.

What is needed on the API side

To make #107 actionable, the /v1/coding_plan/search endpoint needs to accept a pagination mechanism. The simplest options would be:

1. Add a count parameter (1–N, default 10) so callers can request larger pages, and
2. Add an offset or page parameter (1-indexed or 0-indexed) so callers can paginate beyond the first page.

Both should be added to:

• MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py (web_search tool)
• Any underlying API gateway that proxies the request

Once the API supports these, the CLI can be updated to expose --page and --limit flags (and the SDK's SearchSDK.query can accept the same options).

Tracking

Closing the docs gap for #107 in this repo was done in the matching PR. This issue tracks the API-side work.

Refs #107.