Search Wiki
page_searchSearch Yandex Wiki by full text with optional server-side filters for pages, type, dates, or section. Returns ranked pages and files with excerpts, so you can find the right document.
Instructions
Full-text search across the entire Yandex Wiki. Returns results (pages and files) ranked by relevance, each with a title, slug, url, and a text excerpt in content. Two modes: by default one call returns the top limit (up to 50) results and that is the whole reachable set — the response cursors stay null. With highlight=true the search switches to a paginated mode: pages are hard-capped at 10 results no matter the limit, and cursor (the page number echoed back in next_cursor) walks up to ~100 results — deeper than the default mode reaches. The set is over when results comes back empty or next_cursor is null on a non-empty page; past the end next_cursor keeps incrementing over empty pages, so do not treat it alone as 'more exists'. Use this tool to DISCOVER pages, then call page_get with a result's slug to read full content. content is an excerpt of at most ~510 characters cut from wherever the match sits in the page — not the page and not a summary of it, with no guarantee the query terms are even inside it — so treat it as a relevance signal and read the page before answering from it. Wrap multi-word exact phrases in double quotes. All filters (slug_prefix, result_type, authors, dates) run in the search backend itself, before the result limit, so a filtered search does not lose matches to it. To enumerate a section (or the whole Wiki) rather than search it, use page_get_descendants.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Number of search results to return (1-50). Filters are applied by the search backend before this limit, so filtered searches do not need a larger limit to compensate. With highlight=true every page is hard-capped at 10 results, and this value only trims below that cap. | |
| query | Yes | Full-text search query over the whole Wiki. Wrap a multi-word exact phrase in double quotes. | |
| cursor | No | Page number for paging through results, as echoed in `next_cursor` (pages count from 1). Works only together with highlight=true — without it the backend ignores the cursor, so this tool refuses the combination. | |
| authors | No | Optional server-side filter by page owner: a list of user identities (each with uid or cloud_uid), ORed together. Take your own from user_get_current's identity. Omit it to search every author — an empty list is rejected, because it would silently mean the same thing. An unknown identity simply yields no results. | |
| highlight | No | Wrap query matches inside `content` excerpts in <em>…</em> tags. Also a mode switch, not just markup: it caps every page at 10 results regardless of `limit`, and it is the only mode where `cursor` pages deeper (up to ~100 results). | |
| result_type | No | Optional server-side filter by result type. | |
| slug_prefix | No | Optional server-side section filter: only results whose slug equals this prefix or lies under it, e.g. 'tech-doc/ml'. Deep prefixes are fine. An unknown prefix simply yields no results. | |
| created_between | No | Optional server-side filter by creation time. Both bounds are required — the API rejects open intervals. | |
| modified_between | No | Optional server-side filter by last-modification time. Both bounds are required — the API rejects open intervals. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| results | No | ||
| next_cursor | No | ||
| prev_cursor | No |