Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

yandex_search

Read-only

Searches Yandex web results for a query and returns organic results with title, destination URL, display URL, and snippet, with page-based pagination; advertisements are excluded. Use for Russian-language and Eastern-European web research; Yandex occasionally challenges requests, so retry on a 503.

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": {
      "q": "<q>"
    },
    "name": "yandex_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query. Required, e.g. openai.
pageNo1-based result page, default 1, maximum 10.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: ads are excluded, pagination is page-based, and Yandex may return 503s that warrant a retry — operational context an agent could not infer from the annotations.

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?

Two tight sentences, zero filler. The core behavior (organic results, ads excluded) is front-loaded before the usage hint and retry note.

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 an open-world search tool with only two parameters and a rich output schema, the description covers usage context, result scope, and failure handling. It lightly restates return fields the output schema already covers, which is mild redundancy but not harmful.

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 q and page parameters (including the page max of 10) are already documented. The description references pagination but adds no syntax or limits beyond the schema, so baseline 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?

States a precise verb+resource (searches Yandex web results) and enumerates the returned fields (title, destination URL, display URL, snippet). The Yandex-specific scope clearly separates it from the many other search-engine siblings like bing_search, brave_search, and duckduckgo_search.

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

Usage Guidelines4/5

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

"Use for Russian-language and Eastern-European web research" gives a clear condition that selects this tool over other engines. It stops short of naming an explicit alternative for non-Russian queries, so it is strong context without full when-not/exclusion guidance.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources