Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yandex_search

Search Yandex web results and return normalized organic listings with title, URL, display URL, and snippet, plus page-based pagination; ads excluded.

Instructions

Search Yandex web results. Returns normalized organic Yandex web results for a query: title, destination URL, display URL, and snippet, with page-based pagination. Advertisements are not returned. Yandex challenges a portion of requests with a captcha; the service retries across browser profiles and returns 503 if every attempt is challenged, so callers should retry on 503. Results are localized by Yandex to the egress location.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query
pageNo1-based result page; defaults to 1, maximum 10

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the return shape (title, destination URL, display URL, snippet), page-based pagination, that advertisements are excluded, the captcha/503 retry behavior across browser profiles, and that results are localized to the egress location. These are exactly the non-obvious traits an agent needs.

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?

Front-loads the purpose, then layers in output shape, exclusion of ads, error behavior, and localization. Every sentence adds signal, though the captcha/503 sentence is slightly dense. Efficient overall with no filler.

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?

Although there is no output schema, the description enumerates the returned fields and the pagination model, and it covers the main failure mode (503 on captcha) and localization. Nothing an agent needs to invoke and interpret this tool is missing.

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% – both q (query) and page (1-based, default 1, max 10) are documented in the schema itself. The description only restates 'page-based pagination' and adds no syntax or format detail 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?

States a specific verb and resource ('Search Yandex web results') and names the engine explicitly, which differentiates it from the many other web-search siblings (yahoo_search, brave_search, duckduckgo_search, bing_search). It further characterizes the output as organic-only with named result fields.

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?

The description gives operational guidance (retry on 503 due to captcha challenges) but never explains when an agent should choose Yandex over the other search engines in the catalog, nor what Yandex is uniquely good for. Usage is implied by the tool name and search context rather than 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