awaik Yandex Webmaster
Use for Яндекс Вебмастер site checks: hosts, diagnostics, indexing, pages in search, search queries, links, sitemap, recrawl, verification, feeds, and Pro export.
Access Model
- Webmaster uses separate OAuth.
- Do not pass
client_login. - Start with
webmaster_get_hosts. - Use exact
host_idfrom returned hosts. - If
workspace_project_idis selected, only use hosts linked to that project; fail closed if links are absent.
Read Workflow
search_tools({ provider: "yandex", query: "webmaster ..." }).get_tool_schemaforwebmaster_get_hostsand selected read tools.call_toolfor host list, summary, diagnostics, query analytics, sitemap, indexing, and links.- Summarize SEO risks and next actions.
webmaster_query_analytics covers only the last two weeks; for longer periods use webmaster_get_popular_queries or webmaster_get_queries_history with explicit dates. Never claim that Webmaster is not connected while webmaster_* tools are present: verify access with webmaster_check_access and report its actual result.
Write Workflow
Use call_write_tool only after explaining quota/risk and receiving explicit confirmation for:
- adding/deleting host;
- starting verification;
- adding/deleting sitemap;
- requesting recrawl;
- feed changes;
- Pro export start.
Always reread status after write when the API supports it.
Workspace
Do not save Webmaster audits, decisions, or documents without workspace_project_id. If project scope is unclear, call workspace_prepare_project_scope with host_id or domain as external_entity_key.