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

yandex-marketing-mcp

by skiddgoddamn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

yd_webmaster_verification_start

Initiates Yandex Webmaster host ownership verification for a given host using a chosen method such as DNS, meta tag, or file upload.

Instructions

Yandex Webmaster: start host verification with a specified method.

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_id": "<host_id>",
      "verification_type": "<verification_type>"
    },
    "name": "yd_webmaster_verification_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
host_idYesHost ID (from yd_webmaster_hosts_get)
verification_typeYesVerification method

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden but fails to disclose crucial behaviors: whether the process is asynchronous, what the return value indicates, or side effects like DNS changes. It simply states 'start host verification' without detailing outcomes, failure modes, or permissions needed.

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

Conciseness4/5

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

The description is a single sentence with no unnecessary words, achieving conciseness. However, it is slightly under-specified for a tool initiating an action, missing opportunities to add essential context without being verbose.

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 no output schema and missing annotations, the description should explain what the tool returns or confirms. It fails to mention that verification may be asynchronous, that it requires a host to already exist, or any potential errors. This incompleteness hinders correct usage.

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%, so the baseline is 3. The description adds value by linking host_id to yd_webmaster_hosts_get, aiding understanding of its source. However, verification_type only restates 'Verification method' as in schema, adding no new semantic depth.

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 clearly states the verb 'start', resource 'host verification', and specifies 'with a specified method', making the tool's purpose unambiguous. It distinguishes itself from siblings like yd_webmaster_verification_get by indicating it initiates rather than retrieves verification.

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, such as checking existing verification status first or ensuring the host has been added. There are no explicit when-to-use or when-not-to-use instructions, leaving the agent without context for correct invocation.

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