Skip to main content
Glama
artgas1

xmlriver-mcp

by artgas1
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

yandex_search

Read-onlyIdempotent

Parse Yandex search results for a query and region. Get organic listings, related questions, knowledge graph, and date filters for Russian SEO research.

Instructions

Parse Yandex search results page (SERP) for a given query and region.

Use this for: Russian SEO research (own/competitor ranking in Yandex), regional keyword analysis, SERP feature analysis (FAQ, knowledge graph), competitive intel for Russian-speaking markets.

Do NOT use for: keyword frequency data — use wordstat_query instead. Do NOT use for: structured JSON output — use yandex_search_api_v2 instead (official Yandex Search API proxy, cleaner JSON).

Returns: Dict with results (organic 10 items), total_found, page, addresults (related_questions, knowledge_graph, etc), or isError: True on failure.

Examples: yandex_search(query="купить iphone", region=213) → top 10 organic for Moscow

yandex_search(query="site:wildberries.ru игрушки", region=2)
→ site-restricted search for St. Petersburg

yandex_search(query="новости", within="77")
→ last-24-hours filtered

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query. Plain text or with Yandex operators (site:, inurl:, host:, etc). Example: 'купить квартиру москва' or 'site:habr.com nextjs'.
regionNoYandex region ID (lr param). Default 213 (Moscow). Common: 213=Moscow, 2=SPb, 65=Novosibirsk, 54=Yekaterinburg, 47=NN, 10174=Samara, 11119=Krasnodar, 39=Rostov, 51=Kazan. Full list: https://yandex.ru/yandsearch/regions.html
domainNoYandex domain. Default 'ru'.ru
languageNoInterface language. Default 'ru'.ru
deviceNoDevice emulation. Default 'desktop'.desktop
pageNoPage number (0-based for Yandex). Default 0.
withinNoDate filter (Yandex `within` param). Values: '77' (24h), '1' (2 weeks), '2' (1 month), or 'YYYYMMDD..YYYYMMDD' custom range.
additional_blocksNoComma-separated extra blocks: 'topads,bottomads,faqsnippet,rq,rs,knowledge_graph,sitelinks,extended_snippet,fast_links,related_searches'.
filter_duplicatesNoFilter near-duplicate results. Default False (Yandex default).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.6/5.0
Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds that it returns a dict with organic results, total_found, page, addresults, or isError on failure – behavioral context beyond annotations.

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?

Well-structured: introduction, usage guidelines, return format, examples. Sentences are informative without being redundant. Slightly long but appropriate for the tool's complexity.

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

Completeness5/5

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

Covers all aspects: purpose, usage distinctions, parameter behavior via examples, return format, error handling. Output schema exists, but description still explains return dict, making it self-contained for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% (baseline 3). Description provides extra context with examples (e.g., within='77' for 24h, additional_blocks list) and explains query operators, going beyond schema descriptions.

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?

Starts with 'Parse Yandex search results page (SERP) for a given query and region' – specific verb and resource. Differentiates from siblings like wordstat_query and yandex_search_api_v2 via 'Do NOT use for' sections.

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

Usage Guidelines5/5

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

Explicitly lists use cases for Russian SEO, regional keyword analysis, SERP feature analysis. Clearly states when not to use and provides alternative tools (wordstat_query, yandex_search_api_v2).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/artgas1/xmlriver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server