Retrieve a paginated list of sites accessible in your Yandex Webmaster account. Use offset and limit to browse hosts and verify which domains are connected.
Read one bounded page of sites accessible to the server account.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. It says 'Read', which implies a non-destructive operation, but it does not disclose side effects, quotas, error behavior, or any other behavioral details. The 'bounded page' hint is the only additional behavioral clue.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence. Every word contributes meaning, with no redundancy or extraneous details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple paginated list operation, the description provides enough context to perform a basic call. It lacks explicit output format or field details, but no output schema is provided and the operation is straightforward.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema lists limit and offset with defaults but no descriptions. The phrase 'one bounded page' hints at pagination semantics, which indirectly explains the parameters. However, it does not explicitly define limits, defaults, or how offset interacts with paging.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('Read') and the resource ('sites accessible to the server account'), with a pagination qualifier ('one bounded page'). It is unambiguous and distinct from sibling list operations in the same domain.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no explicit guidance on when to use this tool instead of the many sibling webmaster list tools. It does not mention alternatives or selection criteria, leaving the choice to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.