Skip to main content
Glama
Sign In
Yandex Webmaster MCP Server

Yandex Webmaster MCP Server

by weselow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ywm_get_external_links

Retrieve sample external links pointing to your domain to analyze your backlink profile.

Instructions

Get external link samples

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_external_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results
offsetNoOffset
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

C2.8/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It fails to mention pagination (though limit/offset parameters imply it), the optional host_id requirement, or what 'samples' means. The description is too brief to provide meaningful transparency.

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?

The description is extremely concise (4 words), which is efficient but lacks structure and detail. It could be improved by adding a brief explanation of the resource or behavior. It is not wasteful but misses opportunities for clarity.

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 tool has 3 optional parameters and no output schema, the description is insufficient. It does not explain what external links are, how to interpret results, or how this tool relates to siblings like history tools. More context is needed for effective use.

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 the input schema already documents all parameters. The description adds no additional meaning beyond the schema, meeting the baseline of 3. It does not enhance understanding of the parameters.

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?

The description 'Get external link samples' clearly identifies the action (Get) and resource (external links). However, 'samples' is vague and does not clarify if it returns a subset or all links. It distinguishes generically from sibling 'ywm_get_external_links_history' but lacks specificity.

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 like ywm_get_external_links_history or other link-related tools. The description does not mention context such as optional host_id configuration or pagination behavior.

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