Skip to main content
Glama
Sign In
Yandex Webmaster MCP Server

Yandex Webmaster MCP Server

by weselow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ywm_verify_host

Start host verification in Yandex Webmaster by choosing a method: DNS, HTML file, or meta tag. Required to confirm site ownership.

Instructions

Start host verification

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": {
      "verification_type": "<verification_type>"
    },
    "name": "ywm_verify_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idNoHost ID. Optional if YANDEX_WEBMASTER_HOST_URL is configured.
verification_typeYesMethod (DNS, HTML_FILE, META_TAG)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations provided. Description only says 'Start host verification' without disclosing side effects, reversibility, or what happens if host is already verified. Lacks behavioral detail.

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

Conciseness3/5

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

Very concise (one phrase). While not verbose, it is terse and could include more informative details without significant length increase.

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?

No output schema and description does not explain return value (e.g., verification task ID or status). Incomplete for the tool's complexity.

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 baseline is 3. Description adds no additional meaning beyond what schema already provides for both parameters.

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?

Description clearly states action ('Start') and resource ('host verification'). It distinguishes from siblings like ywm_get_verification (get status) and ywm_add_host (add host).

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 on when to use this tool vs alternatives (e.g., prerequisites like adding host first, or when to choose each verification method). Usage context is missing.

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