Skip to main content
Glama

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

by ru.srezai
OverviewDiscussionsAdmin

Скриншот и структура страницы / Page screenshot and structure

fetch_page
Read-onlyIdempotent

Открывает страницу полноценным браузером и возвращает скриншот картинкой прямо в ответе, ссылку на полноразмерный файл и текст страницы в markdown.

Когда: нужно УВИДЕТЬ страницу - раскладку, цвета, типографику, визуальную иерархию: «повтори дизайн как здесь», «что не так с вёрсткой». Когда не: нужен только текст - read_url (1 кредит против 3, и быстрее); нужны отдельные значения - extract. Возвращает: изображение плюс текст. Картинка занимает много контекста, поэтому для чтения этот инструмент избыточен. Если браузер не успел отрендерить страницу, вернём её текст (то же, что даёт read_url), скажем об этом прямо и спишем 1 кредит вместо 3. Цена: 3 кредита (1, если скриншот не получился).

Opens the page in a full browser and returns a screenshot as an inline image, a link to the full-size file, and the page text in markdown.

Use when: you need to SEE the page - layout, colours, typography, visual hierarchy: "match this design", "what looks broken here". Do not use when: you only need text - read_url (1 credit vs 3, and faster); you need specific values - extract. Returns: an image plus text. The image consumes a lot of context, which makes this tool overkill for reading. If the browser fails to render the page, its text is returned instead (the same as read_url), the reply says so, and 1 credit is charged instead of 3. Cost: 3 credits (1 if the screenshot could not be captured).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesПолный URL страницы (http/https) / Full page URL (http/https)
maxCharsNoСколько символов текста вернуть (200-50000, по умолчанию 4000). Поднимите, если нужен полный текст страницы, а не только начало. / How many characters of text to return (200-50000, default 4000). Raise it if you need the whole page text, not just the beginning.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxChars / description
      Previous value: -"Сколько символов текста вернуть (200–50000, по умолчанию 4000). Поднимите, если нужен полный текст страницы, а не только начало. / How many characters of text to return (200–50000, default 4000). Raise it if you need the whole page text, not just the beginning."New value: +"Сколько символов текста вернуть (200-50000, по умолчанию 4000). Поднимите, если нужен полный текст страницы, а не только начало. / How many characters of text to return (200-50000, default 4000). Raise it if you need the whole page text, not just the beginning."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds genuinely new operational context: the cost (3 credits), the fallback path when rendering fails (text returned, 1 credit instead of 3), and the warning that the inline image consumes significant context. This is exactly the behavioural disclosure 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?

Sentences are front-loaded and each carries distinct information (purpose, when/when-not, return shape, fallback, price). It is somewhat inflated by the full Russian/English duplication, which roughly doubles the length without adding information, but the content itself is waste-free.

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, the description fully carries the return contract — image plus full-size link plus markdown text — and even explains the degraded return when rendering fails. An agent has everything needed to decide and to interpret the result.

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 both url and maxChars are already fully documented in the schema, including the 200-50000 range and default. The description adds nothing parameter-specific — it never mentions maxChars or text-length truncation — so the 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 concrete verb and resource — 'opens the page in a full browser' — and enumerates exactly what comes back: an inline screenshot image, a link to the full-size file, and page text in markdown. It is clearly distinguishable from read_url and extract without opening any 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?

Gives an explicit 'when' (visual inspection of layout, colours, typography) and an explicit 'when not', naming the two alternatives by name and the condition that selects each: read_url for text only, extract for specific values. It even quantifies the tradeoff in credits and speed.

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
Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources