Skip to content

docs(search): document the 10-result cap on mmx search query (#107)#170

Open
TumCucTom wants to merge 1 commit into
MiniMax-AI:mainfrom
TumCucTom:fix/cli-107-search-pagination
Open

docs(search): document the 10-result cap on mmx search query (#107)#170
TumCucTom wants to merge 1 commit into
MiniMax-AI:mainfrom
TumCucTom:fix/cli-107-search-pagination

Conversation

@TumCucTom
Copy link
Copy Markdown

@TumCucTom TumCucTom commented Jun 2, 2026

Summary

  • mmx search query's description now spells out the 10-result cap and tells users to refine --q if they need different results.
  • README.md, README_CN.md, and SDK.md get a short note next to the search section making the cap visible.

Why this is a docs-only PR

I investigated the /v1/coding_plan/search endpoint before writing code. The canonical reference client is MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py, where web_search(query: str) only sends {"q": query}. The response is { organic: [...], related_searches: [...] } — no count, page, limit, or offset is accepted or returned.

In other words, the 10-result cap is a hard API limit, not a CLI limitation. Adding --page / --limit flags to the CLI would not actually paginate — the server would ignore them. So this PR is intentionally docs-only.

A follow-up issue has been filed at #169 tracking the API-side work needed to make pagination viable.

Changes

  • src/commands/search/query.ts — extend the command's description (shown in --help) to call out the 10-result cap.
  • README.md / README_CN.md — add a one-line note in the mmx search section.
  • SDK.md — add the same note in the Search subsection.

Test plan

  • bun test — 355 pass, 0 fail
  • bun run typecheck — clean
  • bun run lint — only the 2 pre-existing errors on upstream/main (unrelated to this PR)
  • No new tests needed: this change is description text in a command and prose in docs, with no behavior change.

Refs #107.

The /v1/coding_plan/search endpoint does not currently expose any
pagination parameter (verified against the canonical reference
client at MiniMax-AI/MiniMax-Coding-Plan-MCP/minimax_mcp/server.py,
whose web_search tool only sends {"q": query}). The 10-result cap
is therefore a hard API limit, not a CLI limitation.

Issue MiniMax-AI#107 asked for pagination, but adding --page / --limit
flags to the CLI would not actually paginate — the server would
ignore them. So this PR is docs-only:

- src/commands/search/query.ts: extend the command's --help
  description to call out the 10-result cap and the fact that
  refining --q is the only way to see different results.
- README.md, README_CN.md, SDK.md: add a short note next to
  the search section making the cap visible to users.

The actual fix has to come from the API. A follow-up issue
has been filed at MiniMax-AI#169 tracking the API-side work
needed to make --page and --limit viable.

Refs MiniMax-AI#107.

Co-authored-by: Zippy AI <tomkinsbale@icloud.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant