Skip to main content
Glama
Sign In
yandex-marketing-mcp

yandex-marketing-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

yd_webmaster_host_add

Add a new host URL to Yandex Webmaster for verification. Input the host URL to start the verification process.

Instructions

Yandex Webmaster: add a new host for 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": {
      "host_url": "<host_url>"
    },
    "name": "yd_webmaster_host_add"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations provided. Description says 'add a new host for verification' but doesn't disclose what happens after adding, error conditions, or authorization needs. Agent cannot infer side effects.

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?

Single sentence, front-loaded with key information. No wasted words.

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

Completeness3/5

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

For a simple add tool with one parameter and no output schema, the description is adequate but lacks details on response or post-add state. Could mention success indicators.

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 host_url parameter is well-described in the schema. The main description adds no extra meaning beyond the schema, so baseline 3 applies.

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 states the verb 'add', resource 'host', and purpose 'verification'. It clearly distinguishes from sibling tools like yd_webmaster_host_delete and yd_webmaster_host_get.

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. Among many webmaster siblings, no context on prerequisites (e.g., ownership) or whether host must be new.

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