Skip to main content
Glama
Sign In
Yandex Webmaster MCP Server

Yandex Webmaster MCP Server

by weselow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ywm_get_host

Fetch detailed information about a website host in Yandex Webmaster using its host ID. Enables site management and performance monitoring.

Instructions

Get host details by ID

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ywm_get_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idNoHost ID. Optional if YANDEX_WEBMASTER_HOST_URL is configured.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it lacks any mention of read-only nature, authentication requirements, or what happens when 'host_id' is omitted.

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?

A single sentence that front-loads the purpose with no unnecessary words, earning its place efficiently.

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

Completeness2/5

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

The description is too brief for a tool with no output schema and many siblings. It fails to clarify what 'details' include or how it differs from 'ywm_get_host_summary'.

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 coverage is 100%, and the schema already describes the parameter well. The tool description adds no extra meaning, so the baseline score of 3 is 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 'Get host details by ID' uses a specific verb ('Get') and resource ('host details'), clearly distinguishing it from sibling tools like 'ywm_list_hosts' or 'ywm_get_host_summary'.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives (e.g., 'ywm_list_hosts', 'ywm_get_host_summary'), nor are there any prerequisites or context for its use.

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

Deploy Server

Other Tools