Skip to main content
Glama
Sign In
Yandex Webmaster MCP Server

Yandex Webmaster MCP Server

by theYahia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_user_info

Read-only

Get your Yandex Webmaster user ID to authenticate API requests and manage site data.

Instructions

Get your Yandex Webmaster account info (user_id).

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": "get_user_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoOutput format: 'markdown' (compact, default) or 'json' (raw API response)markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description adds limited extra context. It clarifies the scope ('your' account) and that user_id is the key returned data, but does not disclose additional behavioral details like output structure or rate limits.

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?

The description is a single, front-loaded sentence with no filler. It efficiently conveys the tool's purpose and the key output identifier.

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

Completeness4/5

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

For a simple read-only tool with one optional parameter and clear annotations, the description is sufficient. It mentions the core output (user_id) but does not elaborate on the response format; however, the format parameter allows the user to control that.

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?

The only parameter (format) is fully described in the schema (100% coverage), including its enum values and default. The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 tool retrieves Yandex Webmaster account info (user_id). The verb 'get' and the specific resource 'account info' distinguish it from sibling tools that focus on site diagnostics, queries, or indexing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: use when you need your account info. However, no explicit guidance is given on when this tool should be used over alternatives, nor are there any stated exclusions. The context makes it obvious but it is not explicitly stated.

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