Skip to main content
Glama
Sign In
Yandex Webmaster MCP Server

Yandex Webmaster MCP Server

by weselow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ywm_add_host

Register a new site in Yandex Webmaster by providing its URL. This enables site management and monitoring through the API.

Instructions

Add a new host (site)

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": {
      "host_url": "<host_url>"
    },
    "name": "ywm_add_host"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_urlYesHost URL (e.g. https://example.com)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavioral traits. It does not mention any side effects, authentication needs, rate limits, or what happens upon adding a duplicate host. The description is too minimal for a mutation operation.

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

Conciseness2/5

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

Extremely concise (5 words) but at the expense of necessary details. Important usage and behavioral information is missing, making it under-specified rather than efficiently concise.

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?

Given the simplicity (1 param, no output schema) and lack of annotations, the description should provide more context about the operation's effects, prerequisites, or dependency on other tools (e.g., verification). It falls short.

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 already describes the only parameter (host_url) with 100% coverage. The tool description adds no further meaning beyond the schema, so baseline score of 3 applies.

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

Purpose4/5

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

Description states verb 'Add' and resource 'host (site)', clearly indicating the action and object. It distinguishes from sibling tools like ywm_list_hosts or ywm_delete_host by specifically naming the add operation.

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 versus alternatives (e.g., when to add vs verify or update). No prerequisites, context, or exclusions provided.

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