Skip to main content
Glama

Веб-поиск / Web search

web_search
Read-only

Ищет страницы в живом вебе по текстовому запросу и возвращает ранжированный список: заголовок, ссылка, фрагмент. Сильное покрытие русскоязычного веба.

Instructions

Ищет страницы в живом вебе по текстовому запросу и возвращает ранжированный список: заголовок, ссылка, фрагмент. Сильное покрытие русскоязычного веба.

Когда: нужны свежие факты, ссылки или данные новее вашей отсечки знаний. Когда не: адрес страницы уже известен — это read_url; нужны 2–5 конкретных значений — extract; нужен готовый разбор темы со сносками — deep_research. Возвращает: до 30 результатов текстом, без содержимого страниц. С excerpts: true добавляет реальный текст топ-страниц (+2–4 с), это часто экономит последующий вызов read_url. Цена: 1 кредит за вызов, независимо от num. Выдача живая, поэтому повтор того же запроса даёт другой результат и списывается снова.

Searches the live web by a text query and returns ranked results: title, link, snippet. Strong coverage of the Russian-language web.

Use when: you need fresh facts, links or data past your knowledge cutoff. Do not use when: you already know the page URL — that is read_url; you need a handful of specific values — extract; you need a written answer across many sources — deep_research. Returns: up to 30 results as text, without page content. With excerpts: true it also pulls the actual text of the top pages (+2–4 s), which often saves a follow-up read_url. Cost: 1 credit per call regardless of num. Results are live, so repeating the same query returns different results and is billed again.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numNoСколько результатов (1–30) / How many results (1–30)
depthNoГлубина: auto (по умолчанию, больше движков и результатов) или flash (быстрее, узкая выдача — для одного факта). / Depth: auto (default, more engines and results) or flash (faster, narrow — for a single fact).
queryYesПоисковый запрос / Search query
categoryNoКатегория / Category: general, news, it, science
excerptsNoЗабрать реальный текст топ-страниц под запрос (медленнее на пару секунд, но даёт готовый контент для ответа без доп. переходов). По умолчанию выкл. / Pull the actual text of the top pages for this query (a couple of seconds slower, but gives ready content without extra calls). Off by default.
languageNoЯзык / Language: auto, ru, en
timeRangeNoСвежесть / Recency: '', day, week, month, year
excludeDomainsNoИсключить эти сайты и их поддомены: ["pinterest.com"]. До 10 доменов. / Exclude these sites and their subdomains. Up to 10 domains.
includeDomainsNoИскать только на этих сайтах, вместе с поддоменами: ["habr.com", "vc.ru"]. До 10 доменов. / Search only these sites, including subdomains. Up to 10 domains.
Behavior5/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description goes beyond them by disclosing non-deterministic live results ('repeating the same query returns different results'), cost per call, output limitations (no page content), and the excerpts behavior that adds real text and saves follow-up calls. No contradiction with annotations; in fact, idempotentHint=false aligns with the live Results description.

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?

The description is well-structured with clear sections: purpose, when to use, returns, cost. It is front-loaded with the core purpose, and every sentence adds value. However, it is bilingual (Russian + English), which essentially doubles the length; while valuable for the audience, it slightly reduces conciseness.

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?

The description is comprehensive for a 9-parameter tool with no output schema: it covers return format, limits, cost, live behavior, language coverage, and parameter nuances. The 'when not to use' guidance and excerpts hint make the tool fully usable without further research. Nothing critical is missing.

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 has 100% parameter description coverage, so baseline is 3. The description adds extra nuance beyond the schema for key parameters: excerpts behavior and its cost-saving benefit, depth semantics ('flash' for a single fact), and the relationship between num and max results. It doesn't over-explain, but it compensates beyond the schema's dry definitions.

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 uses a specific verb ('searches the live web') and resource ('web') and clearly states the output format: ranked list with title, link, snippet. It also distinguishes itself from siblings by mentioning 'live web' and 'Russian-language coverage.' This is a model of purpose clarity.

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?

The 'When to use' and 'When not to use' section is explicit and names specific alternatives: read_url for known URLs, extract for 2–5 specific values, deep_research for written answers. It even provides context like needing fresh facts past knowledge cutoff. This is exactly what usage guidance should be.

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/srezai-team/srezai-mcp'

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