Skip to main content
Glama
Yandex Webmaster MCP

Yandex Webmaster MCP

Отправить страницу на переобход

recrawl_url

Submits a page URL to Yandex Webmaster's recrawl queue and returns the task ID plus remaining daily quota, so users can request reindexing and monitor quota limits.

Instructions

Отправляет страницу сайта в очередь на переобход роботом («Переобход страниц»). Возвращает {task_id: UUID, quota_remainder: остаток суточной квоты} со статусом 202. Квота на сайт суточная и зависит от сайта — показывайте пользователю quota_remainder. Ошибки: 400 INVALID_URL — URL не принадлежит сайту или некорректен; 409 URL_ALREADY_ADDED — страница уже в очереди; 429 QUOTA_EXCEEDED — суточная квота исчерпана, попробуйте завтра. 202 означает «в очереди», а не «переобойдена»: сам переобход Яндекс не гарантирует.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "recrawl_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesПолный URL страницы этого сайта, напр. «https://example.com/page».
host_idNoИдентификатор сайта host_id вида «https:example.com:443» (получите из list_sites). Можно не указывать, если задана переменная YANDEX_WEBMASTER_HOST_ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description provides a great deal of behavioral detail beyond the annotations. It explains the response envelope (task_id, quota_remainder) with status 202, the daily per-site quota, and the 400, 409, and 429 error semantics, and it warns that 202 means "queued," not "recrawled." These details are consistent with the annotations: idempotentHint=false matches the 409 URL_ALREADY_ADDED behavior for a repeated call, and destructiveHint=false matches a queue submission.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the action, then the return shape, then the quota rule, then the error table, and the framing note at the end. Every sentence adds value for the caller, and no wording is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, but the description defines the response keys and status code, explains the quota constraint, and enumerates every error path. An agent could invoke this tool and handle all outcomes correctly from the description alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both url and host_id, including the YANDEX_WEBMASTER_HOST_ID fallback, are already documented in the schema. The description adds no parameter-level meaning beyond that, which makes the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: submits a site page to the robot recrawl queue ("Переобход страниц"). No sibling tool performs this action, and the scope (page must belong to the site) is made concrete by the 400 INVALID_URL error case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear operational context: display quota_remainder to the user, and if the 429 QUOTA_EXCEEDED error is raised, retry tomorrow. It does not explicitly tell the agent when to use this tool instead of raw_request or another alternative, but the error codes define the conditions under which the agent should or should not retry.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.