Skip to main content
Glama

срезAI — MCP-сервер и поисковый API для ИИ-агентов

by ru.srezai
OverviewDiscussionsAdmin

Прочитать несколько страниц / Read several pages

read_urls
Read-onlyIdempotent

Читает пачку страниц (до 10 за вызов; на бесплатном тарифе до 5) параллельно и возвращает текст каждой чистым markdown. То же, что read_url, но одним вызовом вместо нескольких - заметно быстрее по общему времени.

Когда: на руках список ссылок, например топ выдачи web_search. Когда не: страница одна - read_url; нужны отдельные поля, а не текст, - extract (он тоже принимает список). Возвращает: текст по каждой странице. Частичный успех - норма: упавшие ссылки не рвут вызов, а перечисляются отдельным блоком «Не прочитано» с кодом ошибки. Дубликаты и ссылки сверх лимита отбрасываются, их число указано в ответе. Длинные страницы обрезаются по maxChars; дочитывать их удобнее по одной через read_url с offset - в батче offset один на все ссылки. Цена: 1 кредит за каждую ссылку - пять страниц стоят пять кредитов. Не отправляйте ссылки «на всякий случай».

Reads a batch of pages (up to 5 per call) in parallel and returns each one's text as clean markdown. Same as read_url but in a single call - markedly faster in total wall-clock.

Use when: you have a list of links, e.g. the top web_search results. Do not use when: there is only one page - read_url; you need specific fields rather than text - extract (it also accepts a list). Returns: text per page. Partial success is normal: failed links do not fail the call, they are listed in a separate "not read" block with an error code. Duplicates and links beyond the limit are dropped and the count is reported. Long pages are cut at maxChars; finish reading them one at a time via read_url with offset - in a batch the offset applies to every link at once. Cost: 1 credit per link - five pages cost five credits. Do not pad the list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesСписок URL (1-10). Дубликаты отбрасываются, лишнее отбрасывается по тарифу: на бесплатном берём 5, на платном 10. / A list of URLs (1-10). Duplicates are dropped; the rest is cut by plan: 5 on the free tier, 10 on paid.
freshNoЧитать все страницы батча заново, не беря недавно прочитанный текст. На цену не влияет. / Read every page in the batch anew instead of using recently read text. Does not affect the price.
engineNoКак забирать страницы: auto (по умолчанию), fast, dynamic, stealth. Применяется ко всем ссылкам батча. / How to fetch the pages: auto (default), fast, dynamic, stealth. Applies to every link in the batch.
maxCharsNoСколько символов текста вернуть с КАЖДОЙ страницы (200-50000, по умолчанию 4000). На батче ставьте скромнее: пять больших страниц вытеснят из контекста всё остальное. / How many characters to return from EACH page (200-50000, default 4000). Keep it modest on a batch: five large pages will crowd everything else out of your context.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / urls / description
      Previous value: -"Список URL (1-5). Дубликаты отбрасываются. / A list of URLs (1-5). Duplicates are dropped."New value: +"Список URL (1-10). Дубликаты отбрасываются, лишнее отбрасывается по тарифу: на бесплатном берём 5, на платном 10. / A list of URLs (1-10). Duplicates are dropped; the rest is cut by plan: 5 on the free tier, 10 on paid."
    • changedInput schema / properties / urls / maxItems
      Previous value: -5New value: +10
  2. Changed2 schema fields changed
    • changedInput schema / properties / maxChars / description
      Previous value: -"Сколько символов текста вернуть с КАЖДОЙ страницы (200–50000, по умолчанию 4000). На батче ставьте скромнее: пять больших страниц вытеснят из контекста всё остальное. / How many characters to return from EACH page (200–50000, default 4000). Keep it modest on a batch: five large pages will crowd everything else out of your context."New value: +"Сколько символов текста вернуть с КАЖДОЙ страницы (200-50000, по умолчанию 4000). На батче ставьте скромнее: пять больших страниц вытеснят из контекста всё остальное. / How many characters to return from EACH page (200-50000, default 4000). Keep it modest on a batch: five large pages will crowd everything else out of your context."
    • changedInput schema / properties / urls / description
      Previous value: -"Список URL (1–5). Дубликаты отбрасываются. / A list of URLs (1–5). Duplicates are dropped."New value: +"Список URL (1-5). Дубликаты отбрасываются. / A list of URLs (1-5). Duplicates are dropped."
  3. Changed1 schema field changed
    • addedInput schema / properties / fresh
      Added value: +{
+  "description": "Читать все страницы батча заново, не беря недавно прочитанный текст. На цену не влияет. / Read every page in the batch anew instead of using recently read text. Does not affect the price.",
+  "type": "boolean"
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description goes well beyond them: partial-failure semantics (failed links are listed in a 'not read' block, they don't fail the call), duplicate and over-limit dropping with reported counts, truncation at maxChars, the batch-level offset limitation, and a per-link credit cost model. This is exactly the operational context annotations cannot carry.

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-loaded with the core purpose, then usage, return behavior, and cost in a logical order; each section earns its place. It is long, however, because the Russian and English versions duplicate the same content, which roughly doubles the token footprint for a single-call read tool.

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?

With no output schema and four parameters, the description fully carries the burden: it states the return format (markdown text per page), partial-success behavior, error reporting, and the credit cost. Nothing an agent needs to call this correctly 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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: cost implications ('1 credit per link - five pages cost five credits'), that fresh does not affect price, that engine and offset apply to the whole batch, and practical guidance on keeping maxChars modest for batches. It stops short of full syntax detail but clearly exceeds the schema's own text.

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+resource+scope: 'Reads a batch of pages ... in parallel and returns each one's text as clean markdown'. It explicitly positions itself relative to siblings ('Same as read_url but in a single call'), so an agent can distinguish it from read_url and extract without opening either schema.

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?

Unusually explicit: 'Use when: you have a list of links, e.g. the top web_search results. Do not use when: there is only one page - read_url; you need specific fields rather than text - extract'. Names both alternatives and the exact condition that selects each.

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

All срезAI — MCP-сервер и поисковый API для ИИ-агентов toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources